[
https://issues.apache.org/jira/browse/HADOOP-13636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510303#comment-15510303
]
Steve Loughran commented on HADOOP-13636:
-----------------------------------------
This is interesting as the warning only surfaces once HdfsConfiguration is
loaded; until then its perfectly fine to use the option: it's in
core-default.xml, and its being used in {{FileSystem.getServerDefaults()}}
—which is indirectly being used in {{org.apache.hadoop.fs.Trash}}.
If it really is deprecated, all uses of it should go —and the deprecation moved
up into hadoop common.
If it isn't really deprecated, then it shouldn't be declared so.
> s3a rm on the CLI generates deprecation warning on io.bytes.per.checksum
> ------------------------------------------------------------------------
>
> Key: HADOOP-13636
> URL: https://issues.apache.org/jira/browse/HADOOP-13636
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Steve Loughran
>
> an rm -r triggers a deprecation warning of {{io.bytes.per.checksum}}. This
> is a property that is not explicitly used anywhere in S3: something else is
> asking for it —something that should switch to the new value
> {code}
> $ ./hadoop fs -rm -r s3a://XYZ/lib
> 16/09/21 16:24:04 WARN util.NativeCodeLoader: Unable to load native-hadoop
> library for your platform... using builtin-java classes where applicable
> 16/09/21 16:24:05 INFO Configuration.deprecation: io.bytes.per.checksum is
> deprecated. Instead, use dfs.bytes-per-checksum
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
