What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
IN operator for vespa querying is not supported.
What is the new behavior (if this is a feature change)?
IN operator is supported in structured indexes only. It also only works on string and int vespa fields.
USER INPUT: List must be surrounded by (). No quotes will be used for list items. Marqo will internally determine whether to treat these like an int or a string. Internal list whitespaces are ignored.
Examples:
a in (1,2,3)
a in (b,c,d)
a in (1, 2, 3)
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
Have unit tests been run against this PR? (Has there also been any additional testing?)
In progress.
Related Python client changes (link commit/PR here)
Related documentation changes (link commit/PR here)
Other information:
Please check if the PR fulfills these requirements
[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Feature
What is the current behavior? (You can also link to an open issue here) IN operator for vespa querying is not supported.
What is the new behavior (if this is a feature change)? IN operator is supported in structured indexes only. It also only works on
stringandintvespa fields.USER INPUT: List must be surrounded by
(). No quotes will be used for list items. Marqo will internally determine whether to treat these like an int or a string. Internal list whitespaces are ignored.Examples:
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No.
Have unit tests been run against this PR? (Has there also been any additional testing?) In progress.
Related Python client changes (link commit/PR here)
Related documentation changes (link commit/PR here)
Other information:
Please check if the PR fulfills these requirements
[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)