You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:09 UTC
[jira] [Updated] (HDDS-998) Remove XceiverClientSpi Interface in
Ozone
[ https://issues.apache.org/jira/browse/HDDS-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-998:
----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> Remove XceiverClientSpi Interface in Ozone
> ------------------------------------------
>
> Key: HDDS-998
> URL: https://issues.apache.org/jira/browse/HDDS-998
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Client
> Affects Versions: 0.4.0
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
>
> Currently, Ratis client and StandAlone client implement the XceiverClientSpi interface. Functionally, XceiverClientRatis supports and requires functionality to handle and update commited log Info of Ratis Servers and same needs to be propagated and handled in Ozone clinet, For the standAlone client, there is no notion of Raft log Index and these functionality make no sense. As Standalone client and Ratis client have diverged functionally, it is logical not to keep a common interface for the two.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org