[ 
https://issues.apache.org/jira/browse/SPARK-24242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyukjin Kwon resolved SPARK-24242.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.0

Issue resolved by pull request 21291
[https://github.com/apache/spark/pull/21291]

> RangeExec should have correct outputOrdering
> --------------------------------------------
>
>                 Key: SPARK-24242
>                 URL: https://issues.apache.org/jira/browse/SPARK-24242
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: Liang-Chi Hsieh
>            Assignee: Liang-Chi Hsieh
>            Priority: Major
>             Fix For: 2.4.0
>
>
> Logical Range node has been added with outputOrdering recently. It's used to 
> eliminate redundant Sort during optimization. However, this outputOrdering 
> info doesn't not propagate to physical Range node. We should use this 
> outputOrdering from logical Range node so parent nodes of Range can correctly 
> know the output ordering.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to