Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/239
@miquillo, would you please expand on your comment on Kinesis Stream
limits? I believe the code so far respects the batch limits for both records
and bytes. The BATCH_SIZE property is validated for 1-500 records (default
250) and flowfiles are pulled from the inbound queues only up to the maximum
number of records and (approximately) the maximum bytes from
MAX_MESSAGE_BUFFER_SIZE_MB.
It's true this processor does NOT throttle the total throughput per second,
but that can be achieved with an upstream ControlRate processor or by
scheduling PutKinesis itself. I don't think we need to address it beyond
capturing the error messages (we do). The defaults seem sensible for most
users.
Do you agree?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
