Skip to content

feat: SQS Large message handling #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 23 commits into from
Aug 31, 2020
Merged

Conversation

msailes
Copy link
Contributor

@msailes msailes commented Aug 31, 2020

Issue #, if available:

Description of changes:

Lambda support for SQS messages which have had their payloads offloaded to S3.

Checklist

Breaking change checklist

RFC issue #:

  • Migration process documented
  • Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@msailes
Copy link
Contributor Author

msailes commented Aug 31, 2020

There is an error building on GitHub because private static AmazonS3 amazonS3 = AmazonS3ClientBuilder.defaultClient(); line 34 in SqsMessageAspect.java expects to be running in an environment where it can find some default information. Such as the region.

Copy link
Contributor

@pankajagrawal16 pankajagrawal16 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few suggestion on docs

<dependency>
<groupId>software.amazon.lambda</groupId>
<artifactId>powertools-sqs</artifactId>
<version>x.x.x</version>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may be update with version latest version here ? or can be done as part of release

}
```

`@LargeMessageHandler` creates a default S3 Client `AmazonS3 amazonS3 = AmazonS3ClientBuilder.defaultClient()`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May be mention a bit explicitly that if download of any message fails from S3 while enriching, entire batch will fail?

@pankajagrawal16
Copy link
Contributor

Build issue is fixed now

@pankajagrawal16 pankajagrawal16 merged commit 7ee5baa into master Aug 31, 2020
@pankajagrawal16 pankajagrawal16 deleted the large-sqs-messages branch August 31, 2020 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants