[HIVE-16330] Improve plans for scalar subquery with aggregates

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Assignee: Vineet Garg
• Reporter: Vineet Garg
• Created: 29/Mar/17 23:08
• Updated: 22/May/18 23:59
• Resolved: 10/May/17 15:29

Description

Scalar subquery plans are generated with a count on subquery which is fed to sq_count_check UDF. This is to make sure at runtime that there is at most one row generated by scalar subquery.

We can avoid generating this extra count for scalar subqueries with aggregates and windowing since such queries are guaranteed to generate at most one row. e.g.

 select * from part where p_size > (select max(p_size) from part) 

Issue Links

• is related to: HIVE-16793 Scalar sub-query: sq_count_check not required if gby keys are constant
• links to: ReviewBoard