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

ASF GitHub Bot commented on HADOOP-8865:
----------------------------------------

zabetak commented on PR #7737:
URL: https://github.com/apache/hadoop/pull/7737#issuecomment-3245395470

   @cnauroth @slfan1989 Thanks for the feedback. Not sure if we should keep 
discussing here or under a new JIRA ticket but here are few thoughts.
   
   The fact that the built-in config files such as `core-default.xml` use 
deprecated properties seems problematic to me. I would argue that once a 
property is deprecated it shouldn't be used anywhere inside the project. If we 
agree on this then maybe we should invest some time to remove/replace existing 
usages of deprecated properties such as `fs.default.name`.
   
   Moreover, the deprecation warnings can be disabled (or directed to another 
file) by end-users by changing the respective logging configuration. I am 
wondering if it is normal/expected to have all logs directed in the console for 
CLI utilities.




> log warn when loading deprecated properties
> -------------------------------------------
>
>                 Key: HADOOP-8865
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8865
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Jianbin Wei
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: BB2015-05-TBR, newbie, pull-request-available
>             Fix For: 3.5.0
>
>         Attachments: HADOOP-8865.patch, HADOOP-8865.patch, HADOOP-8865.patch
>
>
> We need to log warn when loading deprecated properties. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to