[
https://issues.apache.org/jira/browse/FLINK-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18344:
-----------------------------------
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.
> 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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.1#820001)
