[jira] [Updated] (HADOOP-9487) Deprecation warnings in Configuration should go to their own log or otherwise be suppressible

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran updated HADOOP-9487:
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0
                   3.0.0
           Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2. If anyone wants it in 2.1-beta, ask the release manager if its OK and I'll backport it.

(BTW: also added a line ending at the end of {{log4j.properties}} -it was missing one.
                
> 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
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: HADOOP-9487.patch, 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