Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 6 Jun 2013 19:50:20 +0000 (UTC)
From: "Chu Tong (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12643563.1366369743690.80572.1370548220920@arcas>
In-Reply-To: <JIRA.12643563.1366369743690@arcas>
References: <JIRA.12643563.1366369743690@arcas>
Subject: [jira] [Updated] (HADOOP-9487) Deprecation warnings in
 Configuration should go to their own log or otherwise be suppressible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chu Tong updated HADOOP-9487:
-----------------------------

    Status: Patch Available  (was: Open)
    
> Deprecation warnings in Configuration should go to their own log or otherwise be suppressible
> ---------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9487
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9487
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>         Attachments: HADOOP-9487.patch
>
>
> Running local pig jobs triggers large quantities of warnings about deprecated properties -something I don't care about as I'm not in a position to fix without delving into Pig. 
> I can suppress them by changing the log level, but that can hide other warnings that may actually matter.
> If there was a special Configuration.deprecated log for all deprecation messages, this log could be suppressed by people who don't want noisy logs

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira