-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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: Multiple ORDER BY and LIMIT on top of each other leads to incorrect results #71158
Labels
Comments
palesz
added
>bug
:Analytics/SQL
SQL querying
Team:QL (Deprecated)
Meta label for query languages team
labels
Mar 31, 2021
Pinging @elastic/es-ql (Team:QL) |
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
May 12, 2021
Ordering an already pre-ordered and limited subselect is not allowed, as such queries cannot be collapsed and translated into query DSL, but the require an extra ordering step on top of the results returned internally by the search/agg query. Fixes: elastic#71158
matriv
added a commit
that referenced
this issue
May 14, 2021
Ordering an already pre-ordered and limited subselect is not allowed, as such queries cannot be collapsed and translated into query DSL, but the require an extra ordering step on top of the results returned internally by the search/agg query. Fixes: #71158
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
May 14, 2021
Ordering an already pre-ordered and limited subselect is not allowed, as such queries cannot be collapsed and translated into query DSL, but the require an extra ordering step on top of the results returned internally by the search/agg query. Fixes: elastic#71158 (cherry picked from commit a5a20ae)
This was referenced May 14, 2021
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
May 14, 2021
Ordering an already pre-ordered and limited subselect is not allowed, as such queries cannot be collapsed and translated into query DSL, but the require an extra ordering step on top of the results returned internally by the search/agg query. Fixes: elastic#71158 (cherry picked from commit a5a20ae)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The following SELECT gives different results in
ES
vsH2
:It is worth adding at least a check in the Verifier for this.
The text was updated successfully, but these errors were encountered: