Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <27350217.1204953226286.JavaMail.jira@brutus>
Date: Fri, 7 Mar 2008 21:13:46 -0800 (PST)
From: "eric baldeschwieler (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-2885) Restructure the hadoop.dfs package
In-Reply-To: <18157864.1203719359298.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

eric baldeschwieler commented on HADOOP-2885:
---------------------------------------------

I'm struggling to understand all the implications of this.  My intuitions about goals...

1) There should be a top level HDFS sub-project with the servers in it.
2) Any fs.hdfs section of core should contain as little as possible.

3) We need to think about reducing the thrash when we change the FS protocol.  How do these effect that?  A goal should be to provide a stable HDFS interface that isolates Pig and other clients from FS protocol thrash.  This is partially a Pig issue, but it would be terrific if we did not need to recompile a client to run against two dot releases of hadoop.  Do any of these get us closer?  Can we think about this goal while discussing this reorg?


> 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.