hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9487) Deprecation warnings in Configuration should go to their own log or otherwise be suppressible
Date Thu, 06 Jun 2013 20:36:21 GMT

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

Sangjin Lee commented on HADOOP-9487:
-------------------------------------

[~stayhf] I think your patch would change the *default behavior* to disable the deprecation
warnings. Is that intended? I thought the scope of this JIRA was to provide an option of disabling
it but not necessarily change the default behavior. Am I mistaken?
                
> 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

Mime
View raw message