[
https://issues.apache.org/jira/browse/HADOOP-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676334#comment-13676334
]
Steve Loughran commented on HADOOP-9487:
----------------------------------------
I was thinking of having a special logger for deprecation, so you can turn it
off in your Log4J settings by changing the log level from INFO to WARN.
This would bypass the XML conf process entirely
> 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
>
> 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
