[
https://issues.apache.org/jira/browse/FLINK-19460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-19460:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
