[ 
https://issues.apache.org/jira/browse/HIVE-10332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495820#comment-14495820
 ] 

Julian Hyde commented on HIVE-10332:
------------------------------------

No reason to remove LogicalExchange from Calcite, even if Hive doesn't use it.

We could create a LogicalSortExchange in Calcite if Hive would find it useful. 
(Unlike HiveSortExchange, it would have logical convention.)

> Use SortExchange rather than LogicalExchange for HiveOpConverter
> ----------------------------------------------------------------
>
>                 Key: HIVE-10332
>                 URL: https://issues.apache.org/jira/browse/HIVE-10332
>             Project: Hive
>          Issue Type: Sub-task
>          Components: CBO
>            Reporter: Pengcheng Xiong
>            Assignee: Pengcheng Xiong
>             Fix For: cbo-branch
>
>         Attachments: HIVE-10332.01.patch
>
>
> Right now HiveSortExchange extends SortExchange extends Exchange. 
> LogicalExchange extends Exchange. LogicalExchange is expected in 
> HiveOpConverter but HiveSortExchange is created. After discussion, we plan to 
> change LogicalExchange to HiveSortExchange.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to