[SPARK-11036][SQL] AttributeReference should not be assigned new expression id inside tasks #9094
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.
JIRA: https://issues.apache.org/jira/browse/SPARK-11036
Related to #9093, SPARK-11036 is proposed to not allow AttributeReference to be created in executors. #9093 solves part of SPARK-11036. But the method
withExprIdwill possibly assign new expression id to AttributeReference too. This patch tries to prevent that by using the same mechanism of #9093.