You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/08/06 01:36:04 UTC
[jira] [Resolved] (SPARK-9054) Rename RowOrdering to
InterpretedOrdering and use newOrdering to build orderings
[ https://issues.apache.org/jira/browse/SPARK-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen resolved SPARK-9054.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 7973
[https://github.com/apache/spark/pull/7973]
> Rename RowOrdering to InterpretedOrdering and use newOrdering to build orderings
> --------------------------------------------------------------------------------
>
> Key: SPARK-9054
> URL: https://issues.apache.org/jira/browse/SPARK-9054
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Reporter: Josh Rosen
> Assignee: Josh Rosen
> Fix For: 1.5.0
>
>
> There are a few places where we still manually construct RowOrdering instead of using SparkPlan.newOrdering. We should update these to use newOrdering and should rename RowOrdering to InterpretedOrdering to make its function slightly more obvious.
--
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