You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/07/01 22:49:10 UTC
[jira] [Commented] (HDFS-10548) Remove the long deprecated
BlockReaderRemote
[ https://issues.apache.org/jira/browse/HDFS-10548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359780#comment-15359780 ]
Andrew Wang commented on HDFS-10548:
------------------------------------
SGTM, feel free to commit Kai. +1.
> Remove the long deprecated BlockReaderRemote
> --------------------------------------------
>
> Key: HDFS-10548
> URL: https://issues.apache.org/jira/browse/HDFS-10548
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Reporter: Kai Zheng
> Assignee: Kai Zheng
> Attachments: HDFS-10548-v1.patch, HDFS-10548-v2.patch, HDFS-10548-v3.patch
>
>
> To lessen the maintain burden like raised in HDFS-8901, suggest we remove {{BlockReaderRemote}} class that's deprecated very long time ago.
> From {{BlockReaderRemote}} header:
> {quote}
> * @deprecated this is an old implementation that is being left around
> * in case any issues spring up with the new {@link BlockReaderRemote2}
> * implementation.
> * It will be removed in the next release.
> {quote}
> From {{BlockReaderRemote2}} class header:
> {quote}
> * This is a new implementation introduced in Hadoop 0.23 which
> * is more efficient and simpler than the older BlockReader
> * implementation. It should be renamed to BlockReaderRemote
> * once we are confident in it.
> {quote}
> So even further, after getting rid of the old class, we could rename as the comment suggested: BlockReaderRemote2 => BlockReaderRemote.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org