[
https://issues.apache.org/jira/browse/HDDS-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482910#comment-17482910
]
Ritesh H Shukla commented on HDDS-6182:
---------------------------------------
We should be ready to implement the rejection of APIs based on work done in
https://issues.apache.org/jira/browse/HDDS-4731
The 2 use cases for version handling are as follows and everything is in place
to complete the EC and FSO requirements.
# https://issues.apache.org/jira/browse/HDDS-4731 introduced a client version
that can be bumped either once or twice for EC and FSO and older clients can be
rejected or the API behavior can be changed as needed.
# For S3G the client SDK already provides a mechanism to limit a newer client
from talking to an older OM.
> General Purpose Client Versioning
> ---------------------------------
>
> Key: HDDS-6182
> URL: https://issues.apache.org/jira/browse/HDDS-6182
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Client
> Reporter: Ethan Rose
> Assignee: Ritesh H Shukla
> Priority: Major
>
> HDDS-5898 implemented a first draft of client versioning for the s3 gateway
> persistent connections feature. This Jira is to make client versioning a
> general purpose tool that can be applied to specific requests of new features.
> For example:
> * Block a pre-EC client from trying to read an EC key.
> * Block a pre-FSO client from trying to read out of an FSO bucket.
> * Completely block a non-persistent-connection S3 gateway from talking to an
> OM expecting the persistent connection protocol (since rolling upgrades are
> not yet supported).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
