-
Notifications
You must be signed in to change notification settings - Fork 14
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
fix(clients): safer replaceAllObjects + metis compliant #3164
Conversation
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks really good !
|
||
Always wait on the destination index, because: | ||
- it's the only index that we know for sure will exist (since we create it). | ||
- it is Metis compliant, no need for custom implementation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this something we want to expose in a public documentation ? this seems like internal details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's fine, pretty niche documentation, I can ask
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-2407
Changes included:
Add metis compliant implementation for
replaceAllObjects
, also ensure it never hangs if the source index does not exist, detailed explanation in the docs.suggested implementation from @Jerska