Conversation
Contributor
|
@sddonne can you fix here the PR title? The current one always complains at the CI |
sddonne
approved these changes
Apr 13, 2026
bartoval
approved these changes
Apr 13, 2026
Contributor
bartoval
left a comment
There was a problem hiding this comment.
This PR is correct.
Probably, autocomplete in AFTER_AS_CLAUSE needs to be slightly modified -> suggest only the pipe).
bartoval
reviewed
Apr 13, 2026
Contributor
bartoval
left a comment
There was a problem hiding this comment.
Question: Chore change minor or patch, in the version? . Just to avoid to have version 1.10000000.1 in two months.
Contributor
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
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.

This PR updates the ES|QL grammars (lexer and parser) and PromQL grammars to match the latest version in Elasticsearch.
BREAKING CHANGE:
CHANGE POINTcommand options can not longer be written in any order.FROM index | CHANGE_POINT value AS type, pvalue ON keyis no longer syntactically correct.