-
Notifications
You must be signed in to change notification settings - Fork 25.3k
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
ESQL: Add capability to prevent failing tests after Starts/EndsWith Lucene pushdown #124764
Conversation
…With Lucene pushdown
Pinging @elastic/es-analytical-engine (Team:Analytics) |
There was a problem hiding this 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.
💔 Backport failed
You can use sqren/backport to manually backport by running |
…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.
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.