NIFI-15969 Fixed PutS3Object multipart upload data corruption for concurrent FlowFiles with same S3 key#11279
Closed
rakesh-rsky wants to merge 1 commit into
Closed
Conversation
…current FlowFiles with same S3 key Previously the multipart upload state was tracked using only the processor identifier, bucket name, and object key. When two FlowFiles with the same name were uploaded concurrently to the same bucket, they shared the same state tracking key, causing parts from different uploads to be interleaved and resulting in a corrupt S3 object. Included the FlowFile UUID in the state tracking key so each FlowFile maintains its own independent multipart upload state. Retries of the same FlowFile retain the same UUID and continue to benefit from state resumption. A FlowFile with a new UUID starts a fresh upload rather than inheriting stale state.
turcsanyip
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NIFI-15969 Fixed PutS3Object multipart upload data corruption for concurrent FlowFiles with same S3 key.
Previously the multipart upload state was tracked using only the processor identifier, bucket name, and object key. When two FlowFiles with the same name were uploaded concurrently to the same bucket, they shared the same state tracking key, causing parts from different uploads to be interleaved and resulting in a corrupt S3 object.
Fix:
Included the FlowFile UUID in the state tracking key so each FlowFile maintains its own independent multipart upload state. Retries of the same FlowFile retain the same UUID and continue to benefit from state resumption. A FlowFile with a new UUID starts a fresh upload rather than inheriting stale state.
Summary
NIFI-15969
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking
Pull Request Tracking
NIFI-00000NIFI-00000VerifiedstatusPull Request Formatting
mainbranchVerification
Please indicate the verification steps performed prior to pull request creation.
Build
./mvnw clean install -P contrib-checkLicensing
LICENSEandNOTICEfilesDocumentation