[
https://issues.apache.org/jira/browse/HADOOP-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577315#action_12577315
]
dhruba borthakur commented on HADOOP-2885:
------------------------------------------
I vote for Proposal 1. It allows us to ship a new version of HDFS (client and
server) without installing a "core" package. Regarding the question of whether
the wire protocol or the FileSystem API is the "true" interface, I would say
that the FileSystem API is the standard.
At some future time, if Hadoop becomes so popular that it is widely used, Linux
distributions might come pre-packaged with core.jar and hdfs-client.jar
pre-installed. In that case, the HDFS wire protocol becomes sacrosanct and
public. Option 1 allows this scenario too.
> Restructure the hadoop.dfs package
> ----------------------------------
>
> Key: HADOOP-2885
> URL: https://issues.apache.org/jira/browse/HADOOP-2885
> Project: Hadoop Core
> Issue Type: Sub-task
> Components: dfs
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Priority: Minor
> Fix For: 0.17.0
>
> Attachments: Prototype dfs package.png
>
>
> This Jira proposes restructurign the package hadoop.dfs.
> 1. Move all server side and internal protocols (NN-DD etc) to
> hadoop.dfs.server.*
> 2. Further breakdown of dfs.server.
> - dfs.server.namenode.*
> - dfs.server.datanode.*
> - dfs.server.balancer.*
> - dfs.server.common.* - stuff shared between the various servers
> - dfs.protocol.* - internal protocol between DN, NN and Balancer etc.
> 3. Client interface:
> - hadoop.dfs.DistributedFileSystem.java
> - hadoop.dfs.ChecksumDistributedFileSystem.java
> - hadoop.dfs.HftpFilesystem.java
> - hadoop.dfs.protocol.* - the client side protocol
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
