You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/08/13 23:58:45 UTC
[jira] [Commented] (SPARK-9949) TakeOrderedAndProject returns wrong
output attributes when project is pushed in to it
[ https://issues.apache.org/jira/browse/SPARK-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696020#comment-14696020 ]
Apache Spark commented on SPARK-9949:
-------------------------------------
User 'yhuai' has created a pull request for this issue:
https://github.com/apache/spark/pull/8179
> TakeOrderedAndProject returns wrong output attributes when project is pushed in to it
> -------------------------------------------------------------------------------------
>
> Key: SPARK-9949
> URL: https://issues.apache.org/jira/browse/SPARK-9949
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: Yin Huai
> Assignee: Yin Huai
> Priority: Blocker
>
> In {{TakeOrderedAndProject}}, we have
> {code}
> case class TakeOrderedAndProject(
> limit: Int,
> sortOrder: Seq[SortOrder],
> projectList: Option[Seq[NamedExpression]],
> child: SparkPlan) extends UnaryNode {
> override def output: Seq[Attribute] = child.output
> {code}
> When projectList is set, we should use its attributes as the output.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org