-
Notifications
You must be signed in to change notification settings - Fork 141
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
Expected behavior for updates between MIX #840
Comments
Footnotes
|
I've updated the table. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thinking of the following scenario:
For classifier, UPDATE request given in 4. will be lost (overwritten by 5.).
However, for recommender, it persists in sparse_matrix_storage that holds the original feature vectors.
What behavior should I expect in such case for each engine?
The text was updated successfully, but these errors were encountered: