[
https://issues.apache.org/jira/browse/FLINK-30777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Cranmer resolved FLINK-30777.
-----------------------------------
Resolution: Done
> Allow Kinesis Table API Connector to specify shard assigner
> -----------------------------------------------------------
>
> Key: FLINK-30777
> URL: https://issues.apache.org/jira/browse/FLINK-30777
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Reporter: Karthi Thyagarajan
> Assignee: Karthi Thyagarajan
> Priority: Major
> Labels: pull-request-available
> Fix For: aws-connector-4.1.0
>
>
> As a follow up to the fix involving UniformShardAssigner
> (https://issues.apache.org/jira/browse/FLINK-24639), it would be good to
> allow users to pick something other than the default shard assigner, such as
> the recently introduced UniformShardAssigner, in the Kinesis Table API
> Connector.
> This can be accomplished by introducing a new connector option called
> 'shard-assigner.' Something like below; note the introduction of a new option
> called 'shard-assigner'
>
>
> {{CREATE TABLE KinesisTable}}
> (
> `user_id` BIGINT,
> {{`item_id` BIGINT,}}
> {{`category_id` BIGINT,}}
> {{`behavior` STRING,}}
> {{`ts` TIMESTAMP(3))}}
> {{PARTITIONED BY (user_id, item_id)}}
> {{WITH}}
> {{(}}
> {{'connector' = 'kinesis',}}
> {{'stream' = 'user_behavior',}}
> {{'aws.region' = 'us-east-2',}}
> {{'scan.stream.initpos' = 'LATEST',}}
> {{'format' = 'csv',}}
> {{'shard-assigner' = 'uniform'}}
> {{);}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
