-
Notifications
You must be signed in to change notification settings - Fork 25k
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
SQL: consider adding the IN operator support #32955
Labels
Comments
Pinging @elastic/es-search-aggs |
+1
|
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
Oct 18, 2018
Implement the functionality to translate the `field IN (value1, value2,...) expressions to proper Lucene queries or painless script depending on the use case. The `IN` expression can be used in SELECT, WHERE and HAVING clauses. Closes: elastic#32955
This was referenced Oct 18, 2018
matriv
pushed a commit
that referenced
this issue
Oct 23, 2018
Implement the functionality to translate the `field IN (value1, value2,...)` expressions to proper Lucene queries or painless script or local processors depending on the use case. The `IN` expression can be used in SELECT, WHERE and HAVING clauses. Closes: #32955
matriv
pushed a commit
that referenced
this issue
Oct 23, 2018
Implement the functionality to translate the `field IN (value1, value2,...)` expressions to proper Lucene queries or painless script or local processors depending on the use case. The `IN` expression can be used in SELECT, WHERE and HAVING clauses. Closes: #32955
kcm
pushed a commit
that referenced
this issue
Oct 30, 2018
Implement the functionality to translate the `field IN (value1, value2,...)` expressions to proper Lucene queries or painless script or local processors depending on the use case. The `IN` expression can be used in SELECT, WHERE and HAVING clauses. Closes: #32955
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment the workaround for the missing
IN
support is to provide a long list ofOR
statements. It would be easier/more comfortable to useIN
instead.Related to #32942
The text was updated successfully, but these errors were encountered: