You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sahil Takiar (JIRA)" <ji...@apache.org> on 2018/01/26 01:36:00 UTC
[jira] [Created] (HIVE-18552) Split hive.strict.checks.large.query
into two configs, enable partition filter check by default
Sahil Takiar created HIVE-18552:
-----------------------------------
Summary: Split hive.strict.checks.large.query into two configs, enable partition filter check by default
Key: HIVE-18552
URL: https://issues.apache.org/jira/browse/HIVE-18552
Project: Hive
Issue Type: Improvement
Components: Hive
Reporter: Sahil Takiar
{{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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)