[
https://issues.apache.org/jira/browse/HADOOP-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675179#comment-13675179
]
Sangjin Lee commented on HADOOP-9487:
-------------------------------------
I'm not suggesting an implementation yet. :) Could be a boolean variable in the
config or some other flag... If it is part of the config, I presume one needs
to make sure we don't have a circular logic (not that I think there is 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
>
> 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
