-
Notifications
You must be signed in to change notification settings - Fork 33
feat: batch deserialize event records #970
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
base: develop
Are you sure you want to change the base?
Conversation
… extraction in batch processing
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #970 +/- ##
===========================================
+ Coverage 77.47% 77.81% +0.34%
===========================================
Files 271 285 +14
Lines 10900 11402 +502
Branches 1287 1341 +54
===========================================
+ Hits 8445 8873 +428
- Misses 2041 2099 +58
- Partials 414 430 +16 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ler encapsulation
…ng in SQS batch processor
|
Issue number: #969
Summary
Changes
This pull request adds strongly-typed batch processing with automatic deserialization support for SQS, Kinesis, and DynamoDB events.
New Features
Documentation updates
User experience
Introduce strongly-typed batch processing that automatically handles deserialization:
New Interface-based Approach:
Checklist
Please leave checklist items unchecked if they do not apply to your change.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
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.