[
https://issues.apache.org/jira/browse/HDDS-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107224#comment-18107224
]
Chia-Chuan Ho commented on HDDS-16192:
--------------------------------------
Thanks [~szetszwo] , agreed. I’ve created a subtask, "Separate
StorageContainerLocationProtocol RPC identity from its internal Java
interface," and will focus on completing it before making further changes to
the other protocols.
The subtask will preserve the existing FQCN as the RPC/ACL identity, move the
Java service contract to
StorageContainerLocationInternalInterface, and verify the PB metadata,
secure-mode authorization, and HA failover paths. Once completed, we can use it
as the verified procedure for the other protocols.
> Refactor o.a.h.hdds.scm.protocol
> ---------------------------------
>
> Key: HDDS-16192
> URL: https://issues.apache.org/jira/browse/HDDS-16192
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Reporter: Tsz-wo Sze
> Assignee: Chia-Chuan Ho
> Priority: Major
> Labels: pull-request-available
>
> ||interface||protocol (gRPC service)||
> |StorageContainerLocationProtocol|StorageContainerLocationProtocolService|
> |ScmBlockLocationProtocol|ScmBlockLocationProtocolService|
> The above interfaces in package org.apache.hadoop.hdds.scm.protocol are just
> internal interfaces but not really protocols, in the sense that changing the
> signatures of the methods does NOT change the underlying protocols, where the
> underlying protocols are defined in the corresponding gRPC services.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]