[
https://issues.apache.org/jira/browse/HDFS-8053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu updated HDFS-8053:
--------------------------------
Attachment: HDFS-8053.005.patch
Thank you [~wheat9] for your comments. I had a look at the usages of the
{{SecureResources}} class and you're totally correct. I recalled that the
change was brought at the early age of this work when I mistakenly thought we
need to expose the {{TcpPeerServer}} class to {{hadoop-hdfs-client}}. I put the
{{*PeerServer}} classes back to the server side but did not revert all
dependent changes.
The v5 patch reverts the changes of {{SecureResources}}. Meanwhile, I also
double checked every class rename is necessary in order to move the
{{DFSIn/OutputStream}} classes to client side.
> Move DFSIn/OutputStream and related classes to hadoop-hdfs-client
> -----------------------------------------------------------------
>
> Key: HDFS-8053
> URL: https://issues.apache.org/jira/browse/HDFS-8053
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: build
> Reporter: Haohui Mai
> Assignee: Mingliang Liu
> Attachments: HDFS-8053.000.patch, HDFS-8053.001.patch,
> HDFS-8053.002.patch, HDFS-8053.003.patch, HDFS-8053.004.patch,
> HDFS-8053.005.patch
>
>
> This jira tracks the effort of moving the {{DFSInputStream}} and
> {{DFSOutputSream}} classes from {{hadoop-hdfs}} to {{hadoop-hdfs-client}}
> module.
> Guidelines:
> * As the {{DFSClient}} is heavily coupled to these two classes, we should
> move it together.
> * Related classes should be addressed in separate jiras if they're
> independent and complex enough.
> * The checkstyle warnings can be addressed in [HDFS-8979 |
> https://issues.apache.org/jira/browse/HDFS-8979]
> * Removing the _slf4j_ logger guards when calling {{LOG.debug()}} and
> {{LOG.trace()}} can be addressed in [HDFS-8971 |
> https://issues.apache.org/jira/browse/HDFS-8971].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
