[
https://issues.apache.org/jira/browse/HDDS-15193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-15193:
-------------------------------
Fix Version/s: 2.2.0
Resolution: Implemented
Status: Resolved (was: Patch Available)
> Move the "atomic key creation" logic from output stream to S3 endpoints
> -----------------------------------------------------------------------
>
> Key: HDDS-15193
> URL: https://issues.apache.org/jira/browse/HDDS-15193
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Chu Cheng Li
> Assignee: Chu Cheng Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> [https://github.com/apache/ozone/pull/5524]
>
> Remove the "atomic key creation" logic from the Ozone client output stream
> classes and shifts the responsibility for validating S3 object upload content
> length from the client layer to the S3 gateway layer. The main effect is that
> S3-specific length checks are now enforced in the S3 gateway, not in the
> general Ozone client code, leading to a cleaner separation of concerns and
> more maintainable code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
