-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blacklistEvents renamed to blacklistIndicators #241
Comments
Even if using blacklistIndicators parameter, I do not get items filtered: Sending event user 527739 view item ASSET_11637: Fetching recommendations: Query logging: That's why query.user is None and user history is not used to filter out blacklisted indicator items. |
fields has been renamed to rules in URQuery since PredictionIO upgrade. |
My query was using "user" as integer value which caused failure in parseAndValidate. |
I have updated the docs and created PR: actionml/docs.actionml.com#18 |
In this commit "polish docs, move to docs dir":
aa88533#diff-5778ab63eb5a74b5b25b27d166c80b32
Algorithm parameter blacklistEvents was renamed to blacklistIndicators without changing the documentation. I understand it was renamed to match the indicators config. Why was doc not updated? I discovered that blacklistEvents were not showing up in engine status and had to check the coding.
See https://actionml.com/docs/h_ur_config#complete-ur-engine-configuration-specification
"blacklistEvents": ["", "", "", ""],
Author @pferrel
The text was updated successfully, but these errors were encountered: