[
https://issues.apache.org/jira/browse/HIVE-12839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125482#comment-15125482
]
Ashutosh Chauhan commented on HIVE-12839:
-----------------------------------------
[~pxiong] Can you take a look why rule got triggered. It seems like test is
written for a case when it shouldn't be triggered.
However, [~jcamachorodriguez] in cases when it does get triggered, we can
generate a better plan of not adding an extra MR step to enforce limit. For
query in test, pushing limits in previous reduce stage will be sufficient,
since we don't need exact limit to be enforced at that stage. Depending on
data, this extra job actually may slow down the job. It seems like there is a
possibility of improvement here.
> Upgrade Hive to Calcite 1.6
> ---------------------------
>
> Key: HIVE-12839
> URL: https://issues.apache.org/jira/browse/HIVE-12839
> Project: Hive
> Issue Type: Improvement
> Reporter: Pengcheng Xiong
> Assignee: Pengcheng Xiong
> Attachments: HIVE-12839.01.patch, HIVE-12839.02.patch,
> HIVE-12839.03.patch
>
>
> CLEAR LIBRARY CACHE
> Upgrade Hive to Calcite 1.6.0-incubating.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)