[HIVE-12727] refactor Hive strict checks to be more granular, allow order by no limit and no partition filter by default for now

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Labels: TODOC2.0
• Target Version/s: 2.0.0
• Assignee: Sergey Shelukhin
• Reporter: Sergey Shelukhin
• Created: 22/Dec/15 03:16
• Updated: 12/Dec/17 03:47
• Resolved: 29/Jan/16 20:17

Description

Making strict mode the default recently appears to have broken many normal queries, such as some TPCDS benchmark queries, e.g. Q85:
Response message: org.apache.hive.service.cli.HiveSQLException: Error while compiling statement: FAILED: SemanticException [Error 10041]: No partition predicate found for Alias "web_sales" Table "web_returns"

We should remove this restriction from strict mode, or change the default back to non-strict. Perhaps make a 3-value parameter, nonstrict, semistrict, and strict, for backward compat for people who are relying on strict already.

Issue Links

• is related to: HIVE-15148 disallow loading data into bucketed tables (by default)
• is related to: HIVE-18251 Loosen restriction for some checks
• is related to: HIVE-12413 Default mode for hive.mapred.mode should be strict
• relates to: HIVE-14346 Change the default value for hive.mapred.mode to null