[HIVE-14866] Remove logic to set global limit from SemanticAnalyzer

• Type: Improvement
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Target Version/s: 3.0.0
• Assignee: Jesús Camacho Rodríguez
• Reporter: Jesús Camacho Rodríguez
• Created: 30/Sep/16 09:01
• Updated: 27/Feb/24 22:23

Description

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

Issue Links

• relates to: HIVE-15023 SimpleFetchOptimizer needs to optimize limit=0