[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or 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: Minor
> Labels: auto-deprioritized-major, stale-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.3.4#803005)
