You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2019/01/23 14:56:00 UTC
[jira] [Updated] (HDDS-998) Remove XceiverClinetSpi Interface in
Ozone
[ https://issues.apache.org/jira/browse/HDDS-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashikant Banerjee updated HDDS-998:
-------------------------------------
Description: 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. (was: 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 makes no sense to keep a common interface for the two.)
> Remove XceiverClinetSpi Interface in Ozone
> ------------------------------------------
>
> Key: HDDS-998
> URL: https://issues.apache.org/jira/browse/HDDS-998
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Ozone Client
> Affects Versions: 0.4.0
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 0.4.0
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org