ESQL: Unique ids when replacing missing fields #125656
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Collaborator
| Hi @alex-spies, I've created a changelog YAML for you. |
alex-spies commented Mar 27, 2025
| } | ||
| } else if (plan instanceof Project) { | ||
| // Only create null literals for newly encountered missing fields | ||
| plan = resolveAlreadyReplacedAttributes(plan, fieldAttrReplacedBy); |
Contributor Author
| The present approach could lead to class cast exceptions; fixing this introduces incidental complexity. Closing. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Fix #121754
Branched off #125462, but with a different solution.
Requires more local logical plan optimizer tests before this should be merged.