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

Jesus Camacho Rodriguez commented on HIVE-12839:
------------------------------------------------

[~ashutoshc], [~pxiong], I am wondering what is the reason for limit join 
transpose rule to kick in now?
The optimization is configured by an enabling boolean plus a minimum 
proportion/number of rows that the input needs to get reduced; otherwise it 
does not trigger.
Hence, if now it is kicking in and before it was not, are Calcite metadata 
providers working properly with this patch (I saw there was some changes in the 
way we instantiate them)? Otherwise I do not understand why this is happening.

> 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)

Reply via email to