-
Notifications
You must be signed in to change notification settings - Fork 218
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
No user-record aggregation #31
Comments
The data aggregation feature is not currently available but is on our roadmap. Is that the main reason that you always got throttled in #29? |
Yeah pretty much. |
+1 please get to record aggregation. It should help with the cost arguments I'm about to have. |
+1 record aggregation would be big for us |
Same here. Any news re the roadmap plans? Thanks! |
+1 Same here - interested in record aggregation in order to increase throughput. |
For users who stream data for a Kinesis Firehose deliveryStream, we have this option that you can add to your fileFlow "aggregatedRecordSizeBytes" Agent will parse until the last line of your file to which the aggregated bytes is less than or equal to the specified aggregatedRecordSizeBytes. See But we still don't have a solution to Kinesis data streams (kinesisStream) similar to KPL. Having Agent enable KPL is something that we haven't been able to prioritize. |
Any update here? |
Hi,
Unlike the KPL there does not seem to be any userRecord aggregation. This means that we very quickly get throttled on events. Am I missing something? Without this the client is too expensive in terms of kinesis calls across the fleet at high demand.
The text was updated successfully, but these errors were encountered: