Skip to content

Conversation

@ioanatia
Copy link
Contributor

Backports the following commits to 8.x:

* Remove match command

* Remove assertMatchCommand

* Remove unused import
@ioanatia ioanatia requested a review from a team as a code owner September 25, 2024 11:22
@ioanatia ioanatia added :Analytics/ES|QL AKA ESQL >non-issue backport Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) test-release Trigger CI checks against release build labels Sep 25, 2024
@ioanatia
Copy link
Contributor Author

@elasticmachine merge upstream

@ioanatia
Copy link
Contributor Author

@elasticmachine merge upstream

@ioanatia
Copy link
Contributor Author

I merged upstream thinking some of the failures have been solved in the meantime.
Looking at the failures they are unrelated to the changes - I also see some of these changes happening in other PRs.
None of them are ES|QL related.
Leaving this PR open has the potential of making it difficult to merge any other backports that touch the lexer/parser due to conflicts.
I am not a fan of merging by bypassing branch protections, but I will do that in this case.

@DaveCTurner
Copy link
Contributor

Hi @ioanatia, please don't merge things without a clean CI run. Just because it's hitting failures that appear to be unrelated doesn't mean that there aren't other failures later on in the build that are related to this change. We can get into a massive mess if that starts to happen.

Please instead either wait for the problems to be resolved (ping the relevant folks if needed) or else mute the problematic tests yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL backport >non-issue Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) test-release Trigger CI checks against release build v8.16.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants