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/09/20 01:51:44 UTC
[jira] Updated: (HADOOP-4008) Make the Data transfer streaming
protocol concrete
[ https://issues.apache.org/jira/browse/HADOOP-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjay Radia updated HADOOP-4008:
---------------------------------
Description:
The Data transfer between client and datanode and between datanode and datanode is a streaming
protocol where messages and data is sent across a tcp connection.
The messages are not concrete data types (ie they are not classes or interfaces), instead the fields are marshalled and unmarshalled in in various classes.
The message exchange could be made concrete by declaring message data types and/or interfaces.
This will help future automated versioning via protocol-buffers style approach. It will also help document the interface and can simplify the code.
was:
The Client-Datanode streaming protocol is a set of message exchanges.
The messages are not concrete data type s(ie it is not classes or interfaces).
The message exchange could be made concrete by declaring message data types and/or interfaces.
This will help future automated versioning via protocol-buffers style approach. It will also help document the interface and can simplify the code.
Summary: Make the Data transfer streaming protocol concrete (was: Make the Client-Datanode streaming protocol concrete)
> Make the Data transfer streaming protocol concrete
> --------------------------------------------------
>
> Key: HADOOP-4008
> URL: https://issues.apache.org/jira/browse/HADOOP-4008
> Project: Hadoop Core
> Issue Type: Sub-task
> Components: dfs
> Reporter: Sanjay Radia
>
> The Data transfer between client and datanode and between datanode and datanode is a streaming
> protocol where messages and data is sent across a tcp connection.
> The messages are not concrete data types (ie they are not classes or interfaces), instead the fields are marshalled and unmarshalled in in various classes.
> The message exchange could be made concrete by declaring message data types and/or interfaces.
> This will help future automated versioning via protocol-buffers style approach. It will also help document the interface and can simplify the code.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.