Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 26 Jul 2016 21:19:20 +0000 (UTC)
From: "Chao Sun (JIRA)" <jira@apache.org>
To: dev@hive.apache.org
Message-ID: <JIRA.12992728.1469567924000.139291.1469567960823@Atlassian.JIRA>
In-Reply-To: <JIRA.12992728.1469567924000@Atlassian.JIRA>
References: <JIRA.12992728.1469567924000@Atlassian.JIRA> <JIRA.12992728.1469567924127@arcas>
Subject: [jira] [Created] (HIVE-14346) Change the default value for
 hive.mapred.mode to null
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 26 Jul 2016 21:19:23 -0000

Chao Sun created HIVE-14346:
-------------------------------

             Summary: 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


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)