You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Takeshi Yamamuro (Jira)" <ji...@apache.org> on 2020/06/12 22:28:00 UTC
[jira] [Resolved] (SPARK-31977) Returns the projected plan directly
from NestedColumnAliasing
[ https://issues.apache.org/jira/browse/SPARK-31977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Takeshi Yamamuro resolved SPARK-31977.
--------------------------------------
Fix Version/s: 3.1.0
Assignee: Hyukjin Kwon
Resolution: Fixed
Resolved by https://github.com/apache/spark/pull/28812
> Returns the projected plan directly from NestedColumnAliasing
> -------------------------------------------------------------
>
> Key: SPARK-31977
> URL: https://issues.apache.org/jira/browse/SPARK-31977
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Hyukjin Kwon
> Assignee: Hyukjin Kwon
> Priority: Minor
> Fix For: 3.1.0
>
>
> {{NestedColumnAliasing}} and {{GeneratorNestedColumnAliasing}} have a different usage pattern:
> {code}
> case p @ NestedColumnAliasing(nestedFieldToAlias, attrToAliases) =>
> NestedColumnAliasing.replaceToAliases(p, nestedFieldToAlias, attrToAliases)
> {code}
> vs
> {code}
> case GeneratorNestedColumnAliasing(p) => p
> {code}
> It should be better to match it
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org