|
18 | 18 | import org.elasticsearch.transport.RemoteClusterAware; |
19 | 19 | import org.elasticsearch.xpack.core.enrich.EnrichPolicy; |
20 | 20 | import org.elasticsearch.xpack.esql.capabilities.PostAnalysisPlanVerificationAware; |
| 21 | +import org.elasticsearch.xpack.esql.capabilities.PostAnalysisVerificationAware; |
21 | 22 | import org.elasticsearch.xpack.esql.capabilities.TelemetryAware; |
22 | 23 | import org.elasticsearch.xpack.esql.common.Failures; |
23 | 24 | import org.elasticsearch.xpack.esql.core.capabilities.Resolvables; |
|
51 | 52 | import static org.elasticsearch.xpack.esql.core.expression.Expressions.asAttributes; |
52 | 53 | import static org.elasticsearch.xpack.esql.expression.NamedExpressions.mergeOutputAttributes; |
53 | 54 |
|
54 | | -public class Enrich extends UnaryPlan implements GeneratingPlan<Enrich>, PostAnalysisPlanVerificationAware, TelemetryAware, SortAgnostic { |
| 55 | +public class Enrich extends UnaryPlan |
| 56 | + implements |
| 57 | + GeneratingPlan<Enrich>, |
| 58 | + PostAnalysisPlanVerificationAware, |
| 59 | + PostAnalysisVerificationAware, |
| 60 | + TelemetryAware, |
| 61 | + SortAgnostic { |
55 | 62 | public static final NamedWriteableRegistry.Entry ENTRY = new NamedWriteableRegistry.Entry( |
56 | 63 | LogicalPlan.class, |
57 | 64 | "Enrich", |
@@ -326,4 +333,34 @@ private static void checkForPlansForbiddenBeforeRemoteEnrich(Enrich enrich, Fail |
326 | 333 |
|
327 | 334 | badCommands.forEach(c -> failures.add(fail(enrich, "ENRICH with remote policy can't be executed after " + c))); |
328 | 335 | } |
| 336 | + |
| 337 | + /** |
| 338 | + * Remote ENRICH (and any remote operation in fact) is not compatible with MV_EXPAND + LIMIT. Consider: |
| 339 | + * `FROM *:events | SORT @timestamp | LIMIT 2 | MV_EXPAND ip | ENRICH _remote:clientip_policy ON ip` |
| 340 | + * Semantically, this must take two top events and then expand them. However, this can not be executed remotely, |
| 341 | + * because this means that we have to take top 2 events on each node, then expand them, then apply Enrich, |
| 342 | + * then bring them to the coordinator - but then we can not select top 2 of them - because that would be pre-expand! |
| 343 | + * We do not know which expanded rows are coming from the true top rows and which are coming from "false" top rows |
| 344 | + * which should have been thrown out. This is only possible to execute if MV_EXPAND executes on the coordinator |
| 345 | + * - which contradicts remote Enrich. |
| 346 | + * This could be fixed by the optimizer by moving MV_EXPAND past ENRICH, at least in some cases, but currently we do not do that. |
| 347 | + */ |
| 348 | + private void checkMvExpandAfterLimit(Failures failures) { |
| 349 | + this.forEachDown(MvExpand.class, u -> { |
| 350 | + u.forEachDown(p -> { |
| 351 | + if (p instanceof Limit || p instanceof TopN) { |
| 352 | + failures.add(fail(this, "MV_EXPAND after LIMIT is incompatible with remote ENRICH")); |
| 353 | + } |
| 354 | + }); |
| 355 | + }); |
| 356 | + |
| 357 | + } |
| 358 | + |
| 359 | + @Override |
| 360 | + public void postAnalysisVerification(Failures failures) { |
| 361 | + if (this.mode == Mode.REMOTE) { |
| 362 | + checkMvExpandAfterLimit(failures); |
| 363 | + } |
| 364 | + |
| 365 | + } |
329 | 366 | } |
0 commit comments