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

Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2017/07/28 15:23:00 UTC

[jira] [Resolved] (FLINK-7248) Invalid checkRestoredNullCheckpointWhenFetcherNotReady test in FlinkKafkaConsumerBaseTest

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

Tzu-Li (Gordon) Tai resolved FLINK-7248.
----------------------------------------
    Resolution: Fixed

Fixed in master via c5221c85a1c532a5234ec0b4331a04cffa04ba5c.

> Invalid checkRestoredNullCheckpointWhenFetcherNotReady test in FlinkKafkaConsumerBaseTest
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-7248
>                 URL: https://issues.apache.org/jira/browse/FLINK-7248
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector, Tests
>    Affects Versions: 1.4.0
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>             Fix For: 1.4.0
>
>
> The {{checkRestoredNullCheckpointWhenFetcherNotReady}} is a no longer valid remnant from some of the major refactors in the Flink Kafka Consumer, and can be safely removed. The test was passing only because our {{AbstractPartitionDiscoverer}} implementation used in the test base was an empty mock.
> The actual expected behaviour for checkpoints when the fetcher is not read is actually now verified in `checkRestoredCheckpointWhenFetcherNotReady`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)