[HIVE-14346] Change the default value for hive.mapred.mode to null

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.1, 2.2.0
• Fix Version/s: 2.3.0
• Component/s: Configuration
• Labels: TODOC2.2
• Assignee: Chao Sun
• Reporter: Chao Sun
• Created: 26/Jul/16 21:18
• Updated: 22/Sep/17 13:39
• Resolved: 02/Aug/16 16:27

Description

HIVE-12727 introduces three new configurations to replace the existing hive.mapred.mode, which is deprecated. However, the default value for the latter is 'nonstrict', which prevent the new configurations from being used (see comments in that JIRA for more details).

This proposes to change the default value for hive.mapred.mode to null. Users can then set the three new configurations to get more fine-grained control over the strict checking. If user want to use the old configuration, they can set hive.mapred.mode to strict/nonstrict.

Issue Links

• is related to: HIVE-12727 refactor Hive strict checks to be more granular, allow order by no limit and no partition filter by default for now