You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Wang Haihua (JIRA)" <ji...@apache.org> on 2017/09/22 13:40:00 UTC
[jira] [Commented] (HIVE-14346) Change the default value for
hive.mapred.mode to null
[ https://issues.apache.org/jira/browse/HIVE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176431#comment-16176431 ]
Wang Haihua commented on HIVE-14346:
------------------------------------
I just added affect version 2.1.1 because i encounter this issue when hive version 2.1.1.
> Change the default value for hive.mapred.mode to null
> -----------------------------------------------------
>
> Key: HIVE-14346
> URL: https://issues.apache.org/jira/browse/HIVE-14346
> Project: Hive
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.1.1, 2.2.0
> Reporter: Chao Sun
> Assignee: Chao Sun
> Labels: TODOC2.2
> Fix For: 2.3.0
>
> Attachments: HIVE-14346.0.patch, HIVE-14346.1.patch, HIVE-14346.2.patch, HIVE-14346.3.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)