Skip to content

ESQL: Have CombineProjections propagate references upwards #127264

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
merged 4 commits into from
Apr 24, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
[CI] Auto commit changes from spotless
  • Loading branch information
elasticsearchmachine committed Apr 23, 2025
commit 6c1c5bd328b58cada2e2dfed6c417f0d984ba5c6
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,8 @@ public LogicalPlan apply(LogicalPlan plan, LocalLogicalOptimizerContext localLog
// Do not use the attribute name, this can deviate from the field name for union types; use fieldName() instead.
// Also retain fields from lookup indices because we do not have stats for these.
Predicate<FieldAttribute> shouldBeRetained = f -> f.field() instanceof PotentiallyUnmappedKeywordEsField
|| localLogicalOptimizerContext.searchStats().exists(f.fieldName()) || lookupFields.contains(f);
|| localLogicalOptimizerContext.searchStats().exists(f.fieldName())
|| lookupFields.contains(f);

return plan.transformUp(p -> missingToNull(p, shouldBeRetained));
}
Expand Down
Loading