[
https://issues.apache.org/jira/browse/RATIS-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894168#comment-16894168
]
Tsz Wo Nicholas Sze commented on RATIS-612:
-------------------------------------------
Since the requestorId and replyId can be either a ClientId or a RaftPeerId, we
cannot replace the bytes with RaftPeerIdProto (a new message).
Filed RATIS-641 to change RaftPeerId to extend RaftId. Then, we may use
RaftIdProto (a new message) for both ClientId and RaftPeerId.
> Create a protobuf message for RaftPeerId
> ----------------------------------------
>
> Key: RATIS-612
> URL: https://issues.apache.org/jira/browse/RATIS-612
> Project: Ratis
> Issue Type: Improvement
> Components: proto
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Major
> Labels: ozone
>
> Currently, we use bytes for RaftPeerId. It is better to create a protobuf
> message for it as suggested by [~msingh].
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
