Fix ESQL TS requests with LIMIT 0#144031
Merged
leontyevdv merged 13 commits intoelastic:mainfrom Mar 12, 2026
Merged
Conversation
When executing a query using the TS command with STATS dimension_field, a _timeseries column is added in runtime and is taken into account when validating the output. It turns out that "LIMIT 0" is a corner case in which we replace the entire plan with a different one (LocalRelation) so that there is no TimeSeriesAggregate and a verification step fails. Closes elastic#144024
leontyevdv
added
>bug
Team:Analytics
Collaborator
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Collaborator
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
Collaborator
|
Hi @leontyevdv, I've created a changelog YAML for you. |
When executing a query using the TS command with STATS dimension_field, a _timeseries column is added in runtime and is taken into account when validating the output. It turns out that "LIMIT 0" is a corner case in which we replace the entire plan with a different one (LocalRelation) so that there is no TimeSeriesAggregate and a verification step fails. Closes elastic#144024
sidosera
approved these changes
Mar 11, 2026
dnhatn
approved these changes
Mar 11, 2026
Member
dnhatn
left a comment
dnhatn
left a comment
There was a problem hiding this comment.
LGTM. Can you add a csv test for this? Thanks Dima!
…requests' into fix/fix-ts-command-with-limit-0-requests
Contributor
Author
Thanks, Nhat! I added a couple of CSV tests. |
Member
|
Thanks Dima! |
# Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java
# Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Mar 12, 2026
…elocations * upstream/main: (49 commits) CCS logging fixes (elastic#144070) Improve CPS cluster exclusion handling (elastic#143488) Remove snapshot condition now that node_reduce phase is in non-snapshot builds (elastic#144090) Drop deprecation warnings when updating a mapping in the cluster state applier (elastic#143884) (elastic#144040) Add ensureGreenAndNoInitializingShards helper (elastic#144044) Removed unnecessary applies_to blocks from deprecated query (elastic#144096) [CPS] Use single CrossProjectModeDecider instance (elastic#144030) Fix ESQL TS requests with LIMIT 0 (elastic#144031) ESQL: Remove `create` methods in aggs (elastic#144098) ES|QL: Refactor ChangeLimitOperator (elastic#144017) Add Paginated Hit Source Tests (elastic#142592) Fix test failure not preferred (elastic#144019) Remove serialization logic from EIS authorization response (elastic#144021) ESQL: CSV schema inference and parsing enhancements (elastic#144050) ESQL: Fix incorrectly optimized fork with nullify unmapped_fields (elastic#143030) Fix MMR release test using subqueries (elastic#144087) Refactoring `UserAgentPlugin` (elastic#140712) Drop non-finite samples in Prometheus remote write (elastic#144055) [TEST] Wait for internal inference indices to be created in authorization IT (elastic#143885) Disable ndjson datasource QA tests in release-tests (elastic#143992) ...
michalborek
pushed a commit
to michalborek/elasticsearch
that referenced
this pull request
Mar 23, 2026
* Fix ESQL TS requests with LIMIT 0 When executing a query using the TS command with STATS dimension_field, a _timeseries column is added in runtime and is taken into account when validating the output. It turns out that "LIMIT 0" is a corner case in which we replace the entire plan with a different one (LocalRelation) so that there is no TimeSeriesAggregate and a verification step fails. Closes elastic#144024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When executing a query using the TS command with STATS dimension_field, a _timeseries column is added in runtime and is taken into account when validating the output.
It turns out that "LIMIT 0" is a corner case in which we replace the entire plan with a LocalRelation node so that there is no TimeSeriesAggregate and a verification step fails.
Query:
Output:
Closes #144024