flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Schmidt (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FLINK-8980) End-to-end test: BucketingSink
Date Wed, 21 Mar 2018 10:00:00 GMT

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

Florian Schmidt reassigned FLINK-8980:

    Assignee: Florian Schmidt

> End-to-end test: BucketingSink
> ------------------------------
>                 Key: FLINK-8980
>                 URL: https://issues.apache.org/jira/browse/FLINK-8980
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Tests
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: Florian Schmidt
>            Priority: Blocker
>             Fix For: 1.5.0
> In order to verify the {{BucketingSink}}, we should add an end-to-end test which verifies
that the {{BucketingSink}} does not lose data under failures.
> An idea would be to have a CountUp job which simply counts up a counter which is persisted.
The emitted values will be written to disk by the {{BucketingSink}}. Now we should kill randomly
Flink processes (cluster entrypoint and TaskExecutors) to simulate failures. Even after these
failures, the written files should contain the correct sequence of numbers.

This message was sent by Atlassian JIRA

View raw message