GitHub user Renkai opened a pull request:
https://github.com/apache/flink/pull/2847
[FLINK-5031]Consecutive DataStream.split() ignored
I think this is a way to solve this issue, but might not be the best
one.Since I'm knowing the code base enough, I hope someone may review it and
give some advice.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Renkai/flink FLINK-5031
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2847.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2847
----
commit e216c79cd99c08d92847a6254c13fc8d75bb94c3
Author: renkai <[email protected]>
Date: 2016-11-21T06:38:03Z
add a new StreamNode when split
commit 8ce23e658102c35c58946429fd0fde5e72d722df
Author: renkai <[email protected]>
Date: 2016-11-21T07:00:04Z
fix test case
commit 6672354819f2a6411f1a4c9479653f421b6163c6
Author: renkai <[email protected]>
Date: 2016-11-21T07:09:01Z
delete output selectors check since those infos are moved to split1
commit d59900a19c0d966ee175fbbe9661004cec556670
Author: renkai <[email protected]>
Date: 2016-11-21T07:44:58Z
add unit test for consecutive split
commit 8198ee28e95371651d8c159db36dfcf6163c1659
Author: renkai <[email protected]>
Date: 2016-11-22T02:22:16Z
add unit test for consecutive split
commit 2a0d0ec730c1b7d5c955a4ef374ebd7fd6c58f5c
Author: renkai <[email protected]>
Date: 2016-11-22T03:14:37Z
add unit test for consecutive split
commit 410b8717b76df8bfa40b59f1593439442d34ec49
Author: renkai <[email protected]>
Date: 2016-11-22T03:26:18Z
add unit test for consecutive split
commit 290f2f6f6fc1a249cf30d04cc31429e95dc0ec44
Author: renkai <[email protected]>
Date: 2016-11-22T03:50:13Z
add unit test for consecutive split
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---