Feat: add new filter operator "$contains"

[LovaArutinovi]

What kind of change does this PR introduce?

Feature

What is the current behavior?

I need to be able to filter vectors by tag but I can't because there is no way to filter array metadata

What is the new behavior?

I added the new operator "$contains"
now we can have an array in metadata like ['sales', "marketing", "development"]

collection.query(
            data=[...],
            include_metadata=True,
            include_value=True,
            filters={"tags": {"$contains": "development"}})

[olirice]

Note to self:
somehow this renders as

SELECT vecs.bar.id
FROM vecs.bar
WHERE (vecs.bar.metadata -> 'a') @> CAST('1' AS JSONB)
ORDER BY vecs.bar.vec <=> '[0.0, 0.0, 0.0, 0.0, 0.0]'
LIMIT 3

which is exactly correct, but not documented?

[olirice]

Nice PR, thank you

I'm on the fence about what the right behavior for the contains operator on objects and scalars. Could you update the filter to enforce that the metadata field be an json_typeof 'array'? I think that will lead to the least confusion and address the issue that was initially raised.

We can potentially make it broader in the future but narrowing would be difficult to do safely.

[olirice]

update the filter to enforce that the metadata field be an json_typeof 'array'

if you have any trouble with that lmk and I'm happy to do it

[LovaArutinovi]

update the filter to enforce that the metadata field be an json_typeof 'array'

if you have any trouble with that lmk and I'm happy to do it

I will be very grateful if you help🙏

[jeanmaried]

@olirice thank you for merging this! Would you be able to publish a new version soon? We had another PR for deleting by filter that is still unpublished. The last time vecs was published was mid december I believe.

[olirice]

Sure, just published 0.4.3 with current master including this PR