[
https://issues.apache.org/jira/browse/FLINK-34339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hong Liang Teoh resolved FLINK-34339.
-------------------------------------
Resolution: Won't Do
Decided to separate the implementation of KDS and DDB Streams as they are
sufficiently different. DDB Streams has the problem of shard consistency,
whereas KDS does not. The interfaces exposed are also different for DDB Streams
(DescribeStream), versus KDS (ListShards)
> Add connector abstraction layer to remove reliance on AWS SDK classes
> ---------------------------------------------------------------------
>
> Key: FLINK-34339
> URL: https://issues.apache.org/jira/browse/FLINK-34339
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kinesis
> Reporter: Danny Cranmer
> Priority: Major
>
> In order to shim DDB streams we need to be able to support the
> Stream/Shard/Record etc concepts without tying to a specific implementation.
> This will allow us to mimic the KDS/DDB streams support in the old connector
> by providing a shim at the AWS SDK client.
> # Model {{software.amazon.awssdk.services.kinesis}} classes as native
> concepts
> # Push down any usage of {{software.amazon.awssdk.services.kinesis}} to a
> KDS specific class
> # Ensure that the bulk of the connector logic is reusable, the top level
> class would be implementation specific and shim in the write client factories
> and configuration
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
