No EsqlIllegalArgumentException for invalid window values#139470
Merged
kkrik-es merged 3 commits intoelastic:mainfrom Dec 12, 2025
Merged
No EsqlIllegalArgumentException for invalid window values#139470kkrik-es merged 3 commits intoelastic:mainfrom
kkrik-es merged 3 commits intoelastic:mainfrom
Conversation
kkrik-es
added
>bug
Team:StorageEngine
:StorageEngine/ES|QL
Collaborator
|
Hi @kkrik-es, I've created a changelog YAML for you. |
Collaborator
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
parkertimmins
pushed a commit
to parkertimmins/elasticsearch
that referenced
this pull request
Dec 17, 2025
…9470) * No EsqlIllegalArgumentException for invalid window values * Update docs/changelog/139470.yaml * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
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
3 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.
EsqlIllegalArgumentExceptionshouldn't be used to errors related to user-provided inputs as it leads to 500 errors. Instead, lIllegalArgumentException leads to 400s and is thus preferable.