[ https://issues.apache.org/jira/browse/HIVE-18552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sahil Takiar updated HIVE-18552: -------------------------------- Status: Patch Available (was: Open) > Split hive.strict.checks.large.query into two configs > ----------------------------------------------------- > > Key: HIVE-18552 > URL: https://issues.apache.org/jira/browse/HIVE-18552 > Project: Hive > Issue Type: Improvement > Components: Hive > Reporter: Sahil Takiar > Assignee: Sahil Takiar > Priority: Major > Attachments: HIVE-18552.1.patch, HIVE-18552.2.patch, > HIVE-18552.3.patch, HIVE-18552.4.patch > > > {{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)