[
https://issues.apache.org/jira/browse/HIVE-12839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133585#comment-15133585
]
Pengcheng Xiong commented on HIVE-12839:
----------------------------------------
[~ashutoshc] and [~jcamachorodriguez], thanks for your attention. The test
exposed a mistake that I have made. It seems that it is using the default
calcite's getSelectivity for selectivity estimation rather than Hive's
getSelectivity. As a result, the limit remove rule is not triggered and an
extra stage is added. The main reason is that I did not make Hive to initiate
some of the metadataproviders correctly due to the change of CALCITE-794. Now,
I made a full change and it seemed working. I am now waiting for a new QA run.
> 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, HIVE-12839.04.patch
>
>
> CLEAR LIBRARY CACHE
> Upgrade Hive to Calcite 1.6.0-incubating.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
