[
https://issues.apache.org/jira/browse/FLINK-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439531#comment-16439531
]
ASF GitHub Bot commented on FLINK-8980:
---------------------------------------
Github user kl0u commented on the issue:
https://github.com/apache/flink/pull/5813
Thanks for the work @twalthr ! The test looks good but it fails
occasionally due to https://issues.apache.org/jira/browse/FLINK-9113. Given
that the test is unstable, I would suggest to not merge it for now, as it will
lead to unstable builds.
> 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: Timo Walther
> 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
(v7.6.3#76005)
