You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Danny Cranmer (Jira)" <ji...@apache.org> on 2023/05/02 10:08:00 UTC
[jira] [Assigned] (FLINK-31108) Use StreamARN for API calls in Kinesis Connector
[ https://issues.apache.org/jira/browse/FLINK-31108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Cranmer reassigned FLINK-31108:
-------------------------------------
Assignee: Hong Liang Teoh
> Use StreamARN for API calls in Kinesis Connector
> ------------------------------------------------
>
> Key: FLINK-31108
> URL: https://issues.apache.org/jira/browse/FLINK-31108
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Affects Versions: 1.15.3, 1.16.1
> Reporter: Hong Liang Teoh
> Assignee: Hong Liang Teoh
> Priority: Major
> Labels: pull-request-available
>
> Currently, the FlinkKinesisConsumer (Polling + EFO) + FlinkKinesisProducer uses the stream name during API calls
> We want to change this to the StreamARN. There are two reasons for this:
> - This allows lower latency calls to the Kinesis endpoint for GetRecords API
> - Paves the way for allowing user target cross-account streams without assume role (i.e. IAM role in account A but target stream in account B)
>
> The APIs that are currently called:
> * ListShards
> * GetShardIterator
> * GetRecords
> * DescribeStream
> * DescribeStreamSummary
> * DescribeStreamConsumer (already uses StreamARN)
> * RegisterStreamConsumer (already uses StreamARN)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)