[
https://issues.apache.org/jira/browse/HDDS-17532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devesh Kumar Singh updated HDDS-17532:
--------------------------------------
Description:
For explicitly new policy operations, use OM advertised version or a documented
server error path; do not silently acknowledge ignored policy. Preserve legacy
operations and avoid a new ClientVersion unless old-client-specific behavior
makes it necessary.
*Reason:* External client versions are uncontrolled by ZDU.
*Acceptance criteria:* Old-client/new-OM and new-client/old-OM scenarios pass;
policy-free requests unaffected; actionable failure and retry behavior.
was:
Audit and update bucket-create, set/unset-policy and any key-policy APIs in the
RPC client, CLI and OFS. Before sending an explicit new policy request, compare
the receiving OM's advertised capability. Preserve old request behavior when
policy fields are absent. Decide whether ClientVersion is needed only for an
actual server-side distinction of client/response semantics; do not mirror the
OM enum by default. Handle OM failover and server rejection as the final
authority.
*Why:* Client-side gating gives predictable errors and avoids sending
incompatible requests, while OM gating protects state even when the client
check is stale or bypassed.
*Acceptance criteria:* New-client/old-OM request fails clearly;
old-client/new-OM succeeds without policy; no feature loss silently presented
as success; failover covered; ClientVersion addition or non-addition justified.
Summary: Preserve Storage Policy compatibility for Ozone clients, CLI,
and OFS (was: Add Storage Policy compatibility checks to Ozone clients, OFS
and CLI)
> Preserve Storage Policy compatibility for Ozone clients, CLI, and OFS
> ---------------------------------------------------------------------
>
> Key: HDDS-17532
> URL: https://issues.apache.org/jira/browse/HDDS-17532
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone CLI, Ozone Client, Ozone Filesystem
> Reporter: Devesh Kumar Singh
> Priority: Major
>
> For explicitly new policy operations, use OM advertised version or a
> documented server error path; do not silently acknowledge ignored policy.
> Preserve legacy operations and avoid a new ClientVersion unless
> old-client-specific behavior makes it necessary.
> *Reason:* External client versions are uncontrolled by ZDU.
> *Acceptance criteria:* Old-client/new-OM and new-client/old-OM scenarios
> pass; policy-free requests unaffected; actionable failure and retry behavior.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
