Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 19 May 2017 20:50:04 +0000 (UTC)
From: "Chen Liang (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.13073562.1495226953000.253310.1495227004033@Atlassian.JIRA>
In-Reply-To: <JIRA.13073562.1495226953000@Atlassian.JIRA>
References: <JIRA.13073562.1495226953000@Atlassian.JIRA> <JIRA.13073562.1495226953209@jira-lw-us.apache.org>
Subject: [jira] [Created] (HDFS-11857) Ozone : need to refactor
 StorageContainerLocationProtocolServerSideTranslatorPB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 19 May 2017 20:50:10 -0000

Chen Liang created HDFS-11857:
---------------------------------

             Summary: Ozone : need to refactor StorageContainerLocationProtocolServerSideTranslatorPB
                 Key: HDFS-11857
                 URL: https://issues.apache.org/jira/browse/HDFS-11857
             Project: Hadoop HDFS
          Issue Type: Sub-task
            Reporter: Chen Liang
            Assignee: Chen Liang


Currently, StorageContainerLocationProtocolServerSideTranslatorPB has two protocol impls:
{{StorageContainerLocationProtocol impl}}
{{ScmBlockLocationProtocol blockImpl}}.
the class provides container-related services by invoking {{impl}}, and block-related services by invoking {{blockImpl}}. Namely, on server side, the implementation makes a distinguish between "container protocol" and "block protocol". 

An issue is that, currently, everywhere except for the server side is viewing "container protocol" and "block protocol" as different. More specifically, StorageContainerLocationProtocol.proto still includes both container operation and block operation in itself alone. As a result of this difference, it is difficult to implement certain APIs  (e.g. putKey) properly from client side.

This JIRA merges "block protocol" back to "container protocol" in StorageContainerLocationProtocolServerSideTranslatorPB, to unblock the implementation of other APIs for client side. 

Please note that, in the long run, separating these two protocols does seem to be the right way. This JIRA is only a temporary solution to unblock developing other APIs. Will need to revisit these protocols in the future.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org