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

Sanjay Radia commented on HADOOP-2885:
--------------------------------------

FSConstants will need to be refactored  as part of this restructure.
Those that are 
   - for server side (NN, DN, Balancer etc)
          - many of the individual constants can move to the appropriate 
classes but there are probably some that are common across NN, DN
   - for client side classes (DistributedFileSystem and DFSClient)
          - opcodes for the client rpc, time outs etc
   - for applications - these should be moved to hadoop.fs or to config 
defaults. 
          - default block size, max path name etc
                     - are these properties of hadoop.fs or hdfs?

There are probably applications that use come of these constants and hence we 
will need to deprecate FSConstants

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

Reply via email to