You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Chia-Chuan Ho (Jira)" <ji...@apache.org> on 2026/10/19 09:27:00 UTC
[jira] [Created] (HDDS-17147) Separate ScmBlockLocationProtocol RPC identity from its internal Java interface
Chia-Chuan Ho created HDDS-17147:
------------------------------------
Summary: Separate ScmBlockLocationProtocol RPC identity from its internal Java interface
Key: HDDS-17147
URL: https://issues.apache.org/jira/browse/HDDS-17147
Project: Apache Ozone
Issue Type: Sub-task
Reporter: Chia-Chuan Ho
Assignee: Chia-Chuan Ho
Follow-up to HDDS-16243, applying the approach established in HDDS-16247.
ScmBlockLocationProtocol defines the internal Java service contract, while the actual Hadoop RPC protocol is exposed through ScmBlockLocationProtocolPB and ScmBlockLocationProtocolService.
Move the existing Java methods to ScmBlockLocationInternalInterface. Retain ScmBlockLocationProtocol as an empty final class with the same fully qualified class name to preserve the historical RPC protocol identity and service-authorization ACL mapping.
Update implementations, callers, translators, and tracing proxies to use the new internal interface. Preserve existing behavior, PB interfaces, protocol names and versions, Kerberos metadata, and Protobuf definitions.
Verify the PB metadata, secure-mode authentication and authorization, SCM HA failover, and client/server compatibility using existing test coverage where applicable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org