hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chao Sun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14346) Change the default value for hive.mapred.mode to null
Date Tue, 26 Jul 2016 21:52:20 GMT

    [ https://issues.apache.org/jira/browse/HIVE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394610#comment-15394610
] 

Chao Sun commented on HIVE-14346:
---------------------------------

It might. There're a few places which set this to nonstrict, mostly are in tests, but one
in SemanticAnalyzer. I don't think this will break those.


> 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.2.0
>            Reporter: Chao Sun
>            Assignee: Chao Sun
>         Attachments: HIVE-14346.0.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.3.4#6332)

Mime
View raw message