[
https://issues.apache.org/jira/browse/FLINK-19460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327623#comment-17327623
]
Flink Jira Bot commented on FLINK-19460:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> AWS Kinesis Producer EXACTLY_ONCE semantic
> -------------------------------------------
>
> Key: FLINK-19460
> URL: https://issues.apache.org/jira/browse/FLINK-19460
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Reporter: Chris Slotterback
> Priority: Major
> Labels: stale-major
>
> Wanted to create a ticket to discuss adding EXACTLY_ONCE semantics to the AWS
> Kinesis producer, similar to how the Kafka producer functions.
> The kinesis producer would need to be modified to participate in commits, per
> kinesis:
> {noformat}
> Each PutRecords request can support up to 500 records. Each record in the
> request can be as large as 1 MiB, up to a limit of 5 MiB for the entire
> request, including partition keys. Each shard can support writes up to 1,000
> records per second, up to a maximum data write total of 1 MiB per second.
> {noformat}
> Order is not guaranteed when writing to kinesis.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
