andyhuangdev opened a new pull request, #11904:
URL: https://github.com/apache/ozone/pull/11904

   ## What changes were proposed in this pull request?
   Provide a one-liner summary of the changes in the PR **Title** field above.
   It should be in the form of `HDDS-1234. Short summary of the change`.
   
   Please describe your PR in detail:
   * What changes are proposed in the PR? and Why? It would be better if it is 
written from third person's
   perspective not just for the reviewer.
   * Provide as much context and rationale for the pull request as possible. It 
could be copy-paste from
   the Jira's description if the jira is well defined.
   * If it is complex code, describe the approach used to solve the iss## What 
changes were proposed in this pull request?
   
   S3 writes can commit during try-with-resources cleanup when an Error occurs 
after the body is copied but before digest checks and ETag metadata are fully 
registered. The request fails, but unchecked content can replace the previous 
object or become an uploaded part.
   
   This patch requires explicit transfer completion before the write guard 
allows a commit. All seven write blocks mark completion as their final 
statement, after registering metadata and pre-commit checks. Existing length 
and digest validation remain in place.
   
   ## What is the link to the Apache JIRA
   
   [HDDS-17273](https://issues.apache.org/jira/browse/HDDS-17273)
   
   ## How was this patch tested?
   
   - Confirmed eight regression cases fail before the fix, covering post-copy 
errors in PUT and UploadPart, final chunk verification errors, and transfers 
without explicit completion.
   - Added successful completion coverage for empty and non-empty transfers.
   - All 1,932 S3 Gateway unit tests pass.
   - Repository checkstyle and git diff --check pass.ue. If possible attach 
design doc,
   issue investigation, github discussion, etc.
   
   ## What is the link to the Apache JIRA
   
   Please create an issue in ASF JIRA before opening a pull request, and you 
need to set the title of the pull
   request which starts with the corresponding JIRA issue number. (e.g. 
HDDS-XXXX. Fix a typo in YYY.)
   
   If you do not have an ASF Jira account yet, please follow the first-time 
contributor
   instructions in the [Jira guideline](../CONTRIBUTING.md#jira-guideline).
   
   (Please replace this section with the link to the Apache JIRA)
   
   ## How was this patch tested?
   
   (Please explain how this patch was tested. Ex: unit tests, manual tests, 
workflow run on the fork git repo.)
   (If this patch involves UI changes, please attach a screenshot; otherwise, 
remove this.)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to