[
https://issues.apache.org/jira/browse/FLINK-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hong Liang Teoh updated FLINK-18344:
------------------------------------
Fix Version/s: aws-connector-5.2.0
(was: aws-connector-5.1.0)
> Avoid wrong check with shardId in DynamoDB Streams
> --------------------------------------------------
>
> Key: FLINK-18344
> URL: https://issues.apache.org/jira/browse/FLINK-18344
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Affects Versions: 1.10.1
> Reporter: Javier Garcia
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
> Fix For: aws-connector-5.2.0
>
>
> Change class DynamoDBStreamsShardHandle, methodÂ
> isValidShardId to not perform check based on the assumptions of the shardId
> format
> Using localstack as local env for testing, the shardId follow a different
> format, valid following the AWS doc (
> [https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_streams_Shard.html)]
> Can you change the validation to just check the length
--
This message was sent by Atlassian Jira
(v8.20.10#820010)