You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Sanjay Radia (JIRA)" <ji...@apache.org> on 2008/08/23 01:04:44 UTC
[jira] Created: (HADOOP-4005) Cleanup and Document HDFS Client
Intefaces and Protocol
Cleanup and Document HDFS Client Intefaces and Protocol
-------------------------------------------------------
Key: HADOOP-4005
URL: https://issues.apache.org/jira/browse/HADOOP-4005
Project: Hadoop Core
Issue Type: Improvement
Components: dfs
Reporter: Sanjay Radia
Assignee: Sanjay Radia
*Cleanup and Document HDFS Client Intefaces and Protocol*
The HDFS Client Interface/Protocols are
* Client to Namenode RPC protocol
* Client to Datanode RPC protocol
* Client to Datanode Streaming protocol
*Work Items*
* Cleanup FSConstants
* Remove Unnecessary datatypes
** Remove DFSFileInfo - FileStatus is sufficient.
* Make the Client-Datanode streaming protocol concrete
The message exchange could be made concrete by declaring message data types contains the fields being marshaled.
* Declare the exceptions in the interface and also in class FileSystem and rethrow the encapsulated exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4005) Cleanup and Document HDFS Client
Intefaces and Protocol
Posted by "Sanjay Radia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjay Radia updated HADOOP-4005:
---------------------------------
Description:
*Cleanup and Document HDFS Client Intefaces and Protocol*
The HDFS Client Interface/Protocols are
* Client to Namenode RPC protocol
* Client to Datanode RPC protocol
* Client to Datanode Streaming protocol
*Work Items*
* Cleanup FSConstants - HADOOP-4006
* Remove Unnecessary datatypes
** Remove DFSFileInfo - FileStatus is sufficient. - HADOOP-4007
* Make the Client-Datanode streaming protocol concrete - HADOOP-4008
The message exchange could be made concrete by declaring message data types contains the fields being marshaled.
* Declare the exceptions in the interface and also in class FileSystem and rethrow the encapsulated exception. HADOOP-4009
was:
*Cleanup and Document HDFS Client Intefaces and Protocol*
The HDFS Client Interface/Protocols are
* Client to Namenode RPC protocol
* Client to Datanode RPC protocol
* Client to Datanode Streaming protocol
*Work Items*
* Cleanup FSConstants
* Remove Unnecessary datatypes
** Remove DFSFileInfo - FileStatus is sufficient.
* Make the Client-Datanode streaming protocol concrete
The message exchange could be made concrete by declaring message data types contains the fields being marshaled.
* Declare the exceptions in the interface and also in class FileSystem and rethrow the encapsulated exception.
> Cleanup and Document HDFS Client Intefaces and Protocol
> -------------------------------------------------------
>
> Key: HADOOP-4005
> URL: https://issues.apache.org/jira/browse/HADOOP-4005
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
>
> *Cleanup and Document HDFS Client Intefaces and Protocol*
> The HDFS Client Interface/Protocols are
> * Client to Namenode RPC protocol
> * Client to Datanode RPC protocol
> * Client to Datanode Streaming protocol
> *Work Items*
> * Cleanup FSConstants - HADOOP-4006
> * Remove Unnecessary datatypes
> ** Remove DFSFileInfo - FileStatus is sufficient. - HADOOP-4007
> * Make the Client-Datanode streaming protocol concrete - HADOOP-4008
> The message exchange could be made concrete by declaring message data types contains the fields being marshaled.
> * Declare the exceptions in the interface and also in class FileSystem and rethrow the encapsulated exception. HADOOP-4009
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.