You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Hong Liang Teoh (Jira)" <ji...@apache.org> on 2024/09/04 10:43:00 UTC

[jira] [Resolved] (FLINK-36215) Child shards are getting started with LATEST shard iterator even when parents are not expired

     [ https://issues.apache.org/jira/browse/FLINK-36215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hong Liang Teoh resolved FLINK-36215.
-------------------------------------
    Resolution: Fixed

 merged commit [{{4d847fe}}|https://github.com/apache/flink-connector-aws/commit/4d847fee5b18780e2d729975698bf0897205bafe] into   apache:main

> Child shards are getting started with LATEST shard iterator even when parents are not expired
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLINK-36215
>                 URL: https://issues.apache.org/jira/browse/FLINK-36215
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / DynamoDB
>            Reporter: Abhi Gupta
>            Assignee: Abhi Gupta
>            Priority: Major
>              Labels: pull-request-available
>
> While testing, we found out that children are also taking start position as LATEST



--
This message was sent by Atlassian Jira
(v8.20.10#820010)