[Backport] add support to set a prefix for the S3 key #7 #120
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.
IMPORTANT: I'm backporting the PR #118 to
v1
branch.*Issue #7 *
Description of changes:
This PR is adding an new attribute (s3KeyPrefix) for the ExtendedClientConfiguration class that will be used to compose the s3 key.
When the s3KeyPrefix is not null or empty, the S3 key object will use this attribute as prefix of the key. For example, if the s3KeyPrefix is queue-name/, the S3 key will be something like queue-name/676468c5-671f-4471-b9f6-fc5b0a5ab7de.
To keep the current behavior, the method payloadStore.storeOriginalPayload(messageContentStr, s3Key) will be used only if the s3KeyPrefix is not blank.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.