[HIVE-18552] Split hive.strict.checks.large.query into two configs

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Component/s: Hive
• Target Version/s: 3.0.0
• Hadoop Flags: Incompatible change

Release Note

This change splits {{hive.strict.checks.large.query}} into two new configs: {{hive.strict.checks.no.partition.filter}} and {{hive.strict.checks.orderby.no.limit}}

Previously, {{hive.strict.checks.large.query}} controlled whether or not (1) order bys were allowed without limits, and (2) scans on partitioned tables were allowed without filters.

After this change, {{hive.strict.checks.no.partition.filter}} controls the partitioned table check and {{hive.strict.checks.orderby.no.limit}} controls the order by check.

• Assignee: Sahil Takiar
• Reporter: Sahil Takiar
• Created: 26/Jan/18 01:35
• Updated: 22/May/18 23:15
• Resolved: 03/Feb/18 02:45

Description

hive.strict.checks.large.query controls the strict checks for restricting order bys with no limits, and scans of a partitioned table without a filter on the partition table.

While both checks prevent "large" queries from being run, they both control very different behavior. It would be better if users could control these restrictions separately.

Furthermore, many users make the mistake of abusing partitioned tables and often end up in a situation where they are running queries that are doing full-table scans of partitioned tables. This can lead to lots of issues for Hive - e.g. OOM issues because so many partitions are loaded in memory. So it would be good if we enabled this restriction by default.

Issue Links

• links to: RB