Skip to content

Conversation

@HyukjinKwon
Copy link
Member

What changes were proposed in this pull request?

This proposes a minor refactoring to match NestedColumnAliasing to GeneratorNestedColumnAliasing so it returns the pruned plan directly.

    case p @ NestedColumnAliasing(nestedFieldToAlias, attrToAliases) =>
      NestedColumnAliasing.replaceToAliases(p, nestedFieldToAlias, attrToAliases)

vs

    case GeneratorNestedColumnAliasing(p) => p

Why are the changes needed?

Just for readability.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Existing tests should cover.

@HyukjinKwon HyukjinKwon requested a review from viirya June 12, 2020 08:24
@SparkQA
Copy link

SparkQA commented Jun 12, 2020

Test build #123911 has finished for PR 28812 at commit d3a9bef.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

Copy link
Member

@viirya viirya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the description correct? I cannot find GeneratorNestedColumnAliasing in the diff.

nvm, I mis-read the description. Just getting up.

@maropu maropu closed this in a620a2a Jun 12, 2020
@maropu
Copy link
Member

maropu commented Jun 12, 2020

okay, thanks! Merged to master.

@HyukjinKwon
Copy link
Member Author

Thanks @viirya and @maropu!

@HyukjinKwon HyukjinKwon deleted the SPARK-31977 branch July 27, 2020 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants