-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Feature]: The array attribute of the JSON data type should support intersection queries. #25162
Comments
Hi @pofey Would you like to contribute this feature? |
I'm sorry, I just stated my needs. Did I choose the wrong category? |
Nope, feel free to open issues. we will put the feature in backlog until someone working on it. |
Thank you for your support. Could I know approximately how long it would take to complete this support? |
The support for the array type is already on the roadmap and is expected to be available in the 2.3.x series around August, If it doesn't go smoothly, it will go to a later version. Functions like intersection and difference will be supported first on the array type. |
I thought these on two different functionalities? |
@xiaofan-luan @pofey We currently do not support lists, but this requirement can be converted to |
@xiaofan-luan Additionally, I think that to fulfill this requirement, it would be beneficial to introduce a new function called |
/assign |
Is there a reason json_contains can not cover it? |
It can achieve this functionality by combining |
trace by #25276 |
track the feature in #25276, close it |
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
json data:
{ "genre": ["comedy", "documentary"] }
I need to query data where the genre includes 'documentary' and 'plot' values, which is currently not supported. However, Pinecone can implement this with the $in keyword.
For example, queries with the following filters will match the vector:
{"genre": {"$in":["documentary","action"]}}
Describe the solution you'd like.
No response
Describe an alternate solution.
No response
Anything else? (Additional Context)
No response
The text was updated successfully, but these errors were encountered: