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
This issue tracks the feature request to significantly improve the string filtering capabilities within Chroma's metadata. Currently, string filtering is limited to basic equality checks, which is insufficient for many real-world use cases that require partial matches, pattern matching, and more sophisticated string comparisons.
Additional operators users have asked for include:
$contains (or equivalent): To check if a string metadata field contains a specific substring.
$not_contains (or equivalent): To check if a string metadata field does not contain a specific substring.
$like (or equivalent): To support SQL-LIKE pattern matching using wildcards (e.g., % for zero or more characters, _ for a single character).
$regex (or equivalent): To enable filtering based on regular expressions for advanced pattern matching.
Describe the problem
This issue tracks the feature request to significantly improve the string filtering capabilities within Chroma's metadata. Currently, string filtering is limited to basic equality checks, which is insufficient for many real-world use cases that require partial matches, pattern matching, and more sophisticated string comparisons.
Additional operators users have asked for include:
$contains
(or equivalent): To check if a string metadata field contains a specific substring.$not_contains
(or equivalent): To check if a string metadata field does not contain a specific substring.$like
(or equivalent): To support SQL-LIKE pattern matching using wildcards (e.g.,%
for zero or more characters,_
for a single character).$regex
(or equivalent): To enable filtering based on regular expressions for advanced pattern matching.Related user issues:
Describe the proposed solution
To discuss
Alternatives considered
No response
Importance
nice to have
Additional Information
No response
The text was updated successfully, but these errors were encountered: