-
Notifications
You must be signed in to change notification settings - Fork 130
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
upload_records() calls in _migrate_collection() should use wait=True #403
Comments
I would like to take on this issue. After reviewing the code, I understand that the calls to |
…during client migration. The problem was due to missing in the calls. This commit adds to ensure proper synchronization and resolves the vector count mismatch.
* Addresses issue #403 where the vector counts were inconsistent during client migration. The problem was due to missing in the calls. This commit adds to ensure proper synchronization and resolves the vector count mismatch. * Update qdrant_client/migrate/migrate.py * Update qdrant_client/migrate/migrate.py --------- Co-authored-by: George <[email protected]>
Thanks for highlighting this issue! I believe the main issue with The remaining part of it with a corner case should be fixed with #428 and available with the next release, thanks @shivas1516 Feel free to re-open the issue if the problems is reproducible in |
* Addresses issue #403 where the vector counts were inconsistent during client migration. The problem was due to missing in the calls. This commit adds to ensure proper synchronization and resolves the vector count mismatch. * Update qdrant_client/migrate/migrate.py * Update qdrant_client/migrate/migrate.py --------- Co-authored-by: George <[email protected]>
Since the calls to upload_records (here and here) in _migrate_collection() do not use
wait=True
(which defaults toFalse
), the assertion statement at the end of the function that checks that the vector counts match often fails when migrating content from a local client to a remote client. Since we are checking that they match, we should wait for any uploads to complete for consistency, so this should either be set towait=True
directly or at least be exposed as a kwarg for users. Thanks!The text was updated successfully, but these errors were encountered: