Skip to content
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

Pinecone tests fail because of their new handling of null values #590

Open
anakin87 opened this issue Mar 16, 2024 · 0 comments
Open

Pinecone tests fail because of their new handling of null values #590

anakin87 opened this issue Mar 16, 2024 · 0 comments
Labels
bug Something isn't working integration:pinecone

Comments

@anakin87
Copy link
Member

Two tests have recently started to fail.

It is all related to a new handling of null values by Pinecone.

{field: {"$ne": value}} now returns only documents where the field is set and different from value. Previously, it also returned documents where the field was missing. This seems inconsistent with MongoDB filters (from which Pinecone takes its inspiration). Currently, there is no clean way to fix this, because they do not support the $exists operator.

Similarly, {'$or': [{'number': {'$eq': 100}}, {'name': {'$eq': 'name_0'}}]}
only selects documents where both fields are set. This test also fails.

Metadata filtering in Pinecone seems to be a work in progress, so I would propose to skip these failing tests for the time being and rework the filters when the mechanism is more stable on their end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working integration:pinecone
Projects
None yet
Development

No branches or pull requests

1 participant