[
https://issues.apache.org/jira/browse/HIVE-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengcheng Xiong updated HIVE-14866:
-----------------------------------
Target Version/s: 3.0.0 (was: 2.2.0)
> Remove logic to set global limit from SemanticAnalyzer
> ------------------------------------------------------
>
> Key: HIVE-14866
> URL: https://issues.apache.org/jira/browse/HIVE-14866
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 2.1.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Attachments: HIVE-14866.02.patch, HIVE-14866.03.patch,
> HIVE-14866.patch
>
>
> Currently, we set up the global limit for the query in the SemanticAnalyzer.
> In addition, we have an optimization rule GlobalLimitOptimizer that prunes
> the input depending on the global limit and under certain conditions (off by
> default).
> We would like to remove the dependency on the SemanticAnalyzer and set the
> global limit within GlobalLimitOptimizer.
> Further, we need to solve the problem with SimpleFetchOptimizer, which only
> checks the limit but does not take into account the offset of the query,
> which I think might lead to incorrect results if FetchOptimizer kicks in (not
> verified yet).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
