[ 
https://issues.apache.org/jira/browse/HDDS-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Elek, Marton reassigned HDDS-378:
---------------------------------

    Assignee: Elek, Marton

> Remove dependencies between hdds/ozone and hdfs proto files
> -----------------------------------------------------------
>
>                 Key: HDDS-378
>                 URL: https://issues.apache.org/jira/browse/HDDS-378
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: newbie
>
> It would be great to make the hdds/ozone proto files independent from hdfs 
> proto files. It would help as to start ozone with multiple version of hadoop 
> version.
> Also helps to make artifacts from the hdds protos:  HDDS-220
>  Currently we have a few unused "hdfs.proto" import in the proto files and we 
> use the StorageTypeProto from hdfs:
> {code}
> cd hadoop-hdds
> grep -r "hdfs" --include="*.proto"
> common/src/main/proto/ScmBlockLocationProtocol.proto:import "hdfs.proto";
> common/src/main/proto/StorageContainerLocationProtocol.proto:import 
> "hdfs.proto";
>  cd ../hadoop-ozone
> grep -r "hdfs" --include="*.proto"
> common/src/main/proto/OzoneManagerProtocol.proto:import "hdfs.proto";
> common/src/main/proto/OzoneManagerProtocol.proto:    required 
> hadoop.hdfs.StorageTypeProto storageType = 5 [default = DISK];
> common/src/main/proto/OzoneManagerProtocol.proto:    optional 
> hadoop.hdfs.StorageTypeProto storageType = 6;
> {code}
> I propose to 
> 1.) remove the hdfs import statements from the proto files
> 2.) Copy the StorageTypeProto and create a Hdds version from it (without 
> PROVIDED)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to