You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project focuses mainly on supporting Kinesis (de)aggregation in the context of aws lambda. Would it be possible to make the deggregation code more generic so that it can be used to deaggregate records produced by Java KPL?
We have a use case where we produce using Java KPL and consume using python via boto3 client.get_records. There is no builtin support for processing these aggregated records from python: https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-integration.html. The code in deaggregator.py iter_deaggregate_records(records) is coupled to kinesis/lambda but with some refactoring, I think it could satisfy my use case.
The text was updated successfully, but these errors were encountered:
Agreed. Separating the structure of the input event from the base64 decoding and deaggregating should be trivial to implement in the code with backward compatibility. Happy to take a PR on this.
This project focuses mainly on supporting Kinesis (de)aggregation in the context of aws lambda. Would it be possible to make the deggregation code more generic so that it can be used to deaggregate records produced by Java KPL?
We have a use case where we produce using Java KPL and consume using python via boto3 client.get_records. There is no builtin support for processing these aggregated records from python: https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-integration.html. The code in deaggregator.py iter_deaggregate_records(records) is coupled to kinesis/lambda but with some refactoring, I think it could satisfy my use case.
The text was updated successfully, but these errors were encountered: