-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] ES|QL TelemetryIT.testMetrics failure #116003
Comments
Pinging @elastic/es-analytical-engine (Team:Analytics) |
I think it's related to #115813 The underlying error is a query planning problem:
the query is
The failure is quite deterministic, I'll disable that specific query from the telemetry tests to avoid too much noise. @costin maybe you have a clue on the root cause, this test never failed before AFAIK |
Related to #110923 |
Thanks! Needs more investigation since as you said, this test passed so far... |
Backport to 8.x at #116045 |
* ESQL: Refactor Join inside the planner (#115813) First PR that introduces a Join as a first class citizen in the planner. Previously the Join was modeled as a unary node, embedding the right side as a local relationship inside the node but not exposed as a child. This caused a lot the associated methods (like references, output and inputSet) to misbehave and the physical plan rules to pick incorrect information, such as trying to extract the local relationship fields from the underlying source - the fix was to the local relationship fields as ReferenceAttribute (which of course had its own set of issues). Essentially Join was acting both as a source and as a streaming operator. This PR looks to partially address this by: - refactoring Join into a proper binary node with left and right branches which are used for its references and input/outputSet. - refactoring InlineStats to prefer composition and move the Aggregate on the join right branch. This reuses the Aggregate resolution out of the box; in the process remove the Stats interface. - update some of the planner rules that only worked with Unary nodes. - refactor Mapper into (coordinator) Mapper and LocalMapper. - remove Phased interface by moving its functionality inside the planner (no need to unpack the phased classes, the join already indicates the two branches needed). - massage the Phased execution inside EsqlSession - improve FieldExtractor to handle binary nodes - fix incorrect references in Lookup - generalize ProjectAwayColumns rule Relates #112266 Not all inline and lookup tests are passing: - 2 lookup fields are failing due to name clashes (qualifiers should fix this) - 7 or so inline failures with a similar issue I've disabled the tests for now to have them around once we complete adding the functionality. (cherry picked from commit 4ee98e8) * ES|QL: Mute test for #116003 (#116005) (cherry picked from commit 681f509) --------- Co-authored-by: Luigi Dell'Aquila <[email protected]>
This still fails (when unmuted) with current main. We currently do not work on INLINESTATS and the current work on JOINs will likely put INLINESTATS in an even worse state before we come back to it and finish it. That is, until we pick up work on INLINESTATS again, this has to remain muted and this test failure cannot be worked on. |
I think we can drop the usage of INLINESTATS in the test, right? |
That's already done in Luigi's mute. Since the CI failure itself is resolved and we currently don't work on INLINESTATS, maybe it's better to add this failed query to the INLINESTATS follow-up meta issue than having a separate issue for it that'll stay open for a while. |
Moved the corresponding work on INLINESTATS into its meta issue. |
CI Link
https://gradle-enterprise.elastic.co/s/xrzv7jdcyi4ky/console-log/raw
Repro line
./gradlew ":x-pack:plugin:esql:internalClusterTest" --tests "org.elasticsearch.xpack.esql.action.TelemetryIT.testMetrics"
Does it reproduce?
Yes
Applicable branches
main
Failure history
No response
Failure excerpt
The text was updated successfully, but these errors were encountered: