-
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
Empty vectors while scrolling unnamed vector collection #434
Comments
Hi First thing that I see is that there should've been a error on localClient.upsert(
collection_name="namedCol",
points=points
) Because it should not be possible to upsert vectors which were not described during collection creating Regarding the "wrong" records, they are not actually wrong, but the values were normalized. You can change it to |
To insert a named vector your PointStruct(id=1, vector={"text": [0.24, 0.18, 0.22, 0.44]}, payload={"something": "asdf"}), |
I have updated #432 to address the absence of an exception |
I see, so the protection should be done in the upsert side. I was doing the scroll because I wanted to migrate a local database to a remote database, for doing so I could use upsert or upload_records. And for getting the Records I was using scroll. Now I fear that if Records are normalised before giving it to me, when I upload those records the raw data in the remote collection are going to be stored normalised which it is a function of the source collection configuration (models.Distance.COSINE) Is there a way of getting the raw vectors from the scroll records? or should I proceed by using the CollectionPersistence and make the points and upserts to the remote server from there? I am trying to find the most efficient way of pouring one local database into a remote one. |
No, there is currently no way to get the raw vectors Why do you need raw vectors? There is no other way to migrate from local mode to remote We've implemented it in |
try with |
Hi,
This might be a bug, whenever I scroll a collection with named vectors, the records came with an empty vector.
Additionally to the values of the vector in the Record which are completely wrong.
POC
Output
The text was updated successfully, but these errors were encountered: