feat(large-messages): Add function interface for Large Messages Utility#2257
Merged
feat(large-messages): Add function interface for Large Messages Utility#2257
Conversation
|
2 tasks
hjgraca
approved these changes
Nov 3, 2025
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
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.



Summary
This PR introduces an AspectJ-free function API for the Large Messages utility. Instead of annotation a method with
@LargeMessagethe following code can be written (example together with batch processing):This API is thread-safe.
For multi-parameter methods, the following simple pattern can be used:
It is important to note that the utility modifies the
SQSMessagein-place to avoid duplicating large blobs in-memory.Changes
To the reviewers: Ignore PMD findings regarding "Throwable" or "unused parameters". This is expected.
Throwableneeds to be catched for AspectJ compatibilityIssue number: #2212
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.