Skip to content

ESQL: Add capability to prevent failing tests after Starts/EndsWith Lucene pushdown #124764

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

Merged

Conversation

ivancea
Copy link
Contributor

@ivancea ivancea commented Mar 13, 2025

Continuation of #124625, after different issues arised.

Closes #124693
Closes #124745
Closes #124829

The failing BWC tests are checking <8.14 mixed cluster nodes, and SingleValueQuery is sometimes emitting warnings with an empty source.
After some investigation, it's locally reproducible (not 100% of the time though). I was looking for some non-serialized Source that we serialized after that version, but I couldn't find anything relevant. So given that this only impacts warnings in old mixed clusters, this change should be enough.

@ivancea ivancea added >test Issues or PRs that are addressing/adding tests Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) auto-backport Automatically create backport pull requests when merged :Analytics/ES|QL AKA ESQL v8.19.0 v9.0.1 v9.1.0 labels Mar 13, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@costin costin self-requested a review March 13, 2025 16:36
Copy link
Member

@costin costin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
Separately, it's a shame this functionality didn't make it to 8.18 - if it doesn't mess the backporting process I would look into it since the performance implications are significant.

@ivancea
Copy link
Contributor Author

ivancea commented Mar 14, 2025

@costin Working on it. It should be trivial to backport to 8.18.1.
I'll make both backports in the same PR (The original code + the test fixes)

Edit: 8.18 backport: #124871

@ivancea ivancea merged commit f262839 into elastic:main Mar 14, 2025
17 checks passed
@ivancea ivancea deleted the esql-capability-lucene-pushdown-starts-with branch March 14, 2025 10:50
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.x Commit could not be cherrypicked due to conflicts
9.0 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 124764

ivancea added a commit to ivancea/elasticsearch that referenced this pull request Mar 14, 2025
…With Lucene pushdown (elastic#124764)

Continuation of elastic#124641, after different issues arised.

Closes elastic#124693
Closes elastic#124745

The failing BWC tests are checking <8.14 mixed cluster nodes, and SingleValueQuery is sometimes emitting warnings with an empty source.
ivancea added a commit that referenced this pull request Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL auto-backport Automatically create backport pull requests when merged Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test Issues or PRs that are addressing/adding tests v8.19.0 v9.0.1 v9.1.0
Projects
None yet
3 participants