You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: