-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
ESQL: Lower the implicit limit, if none is user-provided #99816
Conversation
This lowers the implicit (max) 10K limit to 500 (default). The new default limit is only added if no other limit is detected after the last pipeline breaker. Otherwise the capping max limit is applied.
If any limit is provided in the query, only apply the max capping.
Pinging @elastic/es-ql (Team:QL) |
Pinging @elastic/elasticsearch-esql (:Query Languages/ES|QL) |
Hi @bpintea, I've created a changelog YAML for you. |
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.
LGTM
@elasticsearchmachine run elasticsearch-ci/part-3 |
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.
LGTM. This needs to be clearly documented.
Opened #99880 |
Document the newly implicit limit of 500 (if no other limit is provided), as well as the global 10K one. Related: #99816
Document the newly implicit limit of 500 (if no other limit is provided), as well as the global 10K one. Related: elastic#99816
Fixes elastic#100555 ESQL [by default](elastic#99816) adds an implicit `LIMIT 500` to queries that do not define a limit. Since this can be confusing for the end user, with this PR we also add a warning to the response, making this default clear and explicit.
This lowers the implicit (max) 10K limit to 500 (default). The new
default limit is only added if no other limit is detected anywhere
in the query (i.e. also before a pipeline breaker, like stats).
Otherwise the capping max limit is applied (as before).
The default limit is made a node setting, like the max results limit.
Closes #99458.