-
Notifications
You must be signed in to change notification settings - Fork 421
Feature request: Support for MSK in Batch Processing #2969
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
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Hello @einarjohnson! In fact this is a nice feature, we see a growing number of customers asking for Batch Processing support on EventSource other than SQS, DynamoDB, and Kinesis. The main benefit of our batch processing utility is the ability to handle partial failures and return only failed messages to the source, and currently, Lambda does not support PartialFailure when using MSK. I will keep this issue open to allow the community to give it a thumbs up and we will pass this need from our customers to the Lambda team. I don't have an estimated date of when I can update this issue with any news, but as soon as I have news I'll come back here to update. Thank you so much for bringing these ideas to Powertools, this is priceless. |
Thanks for the quick response @leandrodamascena . Given the nature of Kafka/consumer offsets this feature might be tricky to implement. But it would be great to have at some stage, very exited to see if this gains some momentum with the AWS lambda team and gets implemented in some way. |
Hello everyone! We don't know if However, we are keeping an eye on all releases from the Lambda/Poller team and if support is added, we will reopen this issue. Thank you. |
|
Use case
Add support for batch processing partial failures when using a MSK/Kafka event source map. This is currently supported for Amazon SQS, Amazon Kinesis Data Streams, and Amazon DynamoDB Streams and it would be great to have this feature for Kafka also.
Solution/User Experience
Having the same interface, or something similar, to what we already have for SQS.
Alternative solutions
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: