-
-
Notifications
You must be signed in to change notification settings - Fork 695
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
add support for TermSetQuery in query parser #1683
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1683 +/- ##
========================================
Coverage 94.03% 94.04%
========================================
Files 256 256
Lines 48956 49066 +110
========================================
+ Hits 46038 46143 +105
- Misses 2918 2923 +5
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
but don't support executing such query
for (i, element) in elements.iter().enumerate() { | ||
if i == 0 { | ||
write!(formatter, "{:?}", element)?; | ||
} else if i == MAX_DISPLAYED - 1 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick. There is a small glitch if elements.len() == MAX_DISPLAYED.
We then display (0 more)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not really user facing so no need to fix.
Add support for creating a
TermSetQuery
from the query parser withfield: IN [val1 val2 val3]