[
https://issues.apache.org/jira/browse/HIVE-14590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453012#comment-15453012
]
Jesus Camacho Rodriguez commented on HIVE-14590:
------------------------------------------------
For the time being, this should be fine. As there might be other cases when the
limit is not the top most operator, but still global limit optimization can be
applied, I think it would be worth to create a follow-up to identify the global
limit for a given query i.e. identifying which specific operators 'reset'
global limit optimization. Could you do that?
+1
> CBO (Calcite Return Path) Incorrect result set when limit is present in one
> of the union branches
> -------------------------------------------------------------------------------------------------
>
> Key: HIVE-14590
> URL: https://issues.apache.org/jira/browse/HIVE-14590
> Project: Hive
> Issue Type: Sub-task
> Components: Logical Optimizer
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Ashutosh Chauhan
> Assignee: Ashutosh Chauhan
> Attachments: HIVE-14590.1.patch, HIVE-14590.patch
>
>
> Limit gets propagated outside union.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
