You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Abhishek Pal (Jira)" <ji...@apache.org> on 2026/02/19 19:00:00 UTC

[jira] [Updated] (HDDS-14665) Add upgrade handling to S3Multipart requests

     [ https://issues.apache.org/jira/browse/HDDS-14665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Pal updated HDDS-14665:
--------------------------------
        Parent:     (was: HDDS-10611)
    Issue Type: Improvement  (was: Sub-task)

> Add upgrade handling to S3Multipart requests
> --------------------------------------------
>
>                 Key: HDDS-14665
>                 URL: https://issues.apache.org/jira/browse/HDDS-14665
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Abhishek Pal
>            Assignee: Abhishek Pal
>            Priority: Major
>
> If we introduce a new schema, new writes may happen while we are in pre-finalize state.
> This means client might start writing with new schema version. But what happens if they want to downgrade from that point?
> So we need to add checks such that if the upgrade finalization has not been done i.e. layout version still doesn't support the split table functionality, new writes should be enforced with *schemaVersion: 0*.
> Similar checks must be added to other requests where if any existing write is happening with schemaVersion: 1 and the layout version doesn't support split table, then we must throw error.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org