[ https://issues.apache.org/jira/browse/BEAM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726461#comment-15726461 ]
ASF GitHub Bot commented on BEAM-1096: -------------------------------------- GitHub user xhumanoid opened a pull request: https://github.com/apache/incubator-beam/pull/1520 [BEAM-1096] flink streaming side output optimization using SplitStream Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-<Jira issue #>] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- @aljoscha check please You can merge this pull request into a Git repository by running: $ git pull https://github.com/xhumanoid/incubator-beam stream_side_output_optimization Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-beam/pull/1520.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 #1520 ---- commit 568d73f74219a42cac4028b198f53f22a832990f Author: Alexey Diomin <diomi...@gmail.com> Date: 2016-12-06T19:30:54Z [BEAM-1096] flink streaming side output optimization using SplitStream ---- > flink streaming side output optimization using SplitStream > ---------------------------------------------------------- > > Key: BEAM-1096 > URL: https://issues.apache.org/jira/browse/BEAM-1096 > Project: Beam > Issue Type: Improvement > Components: runner-flink > Affects Versions: 0.4.0-incubating > Reporter: Alexey Diomin > Priority: Minor > > Current implementation: > 1) send all events in all output streams > 2) filtering streams for necessary tags > Cons: increased cpu usage for serialization all events > Proposed implementation: > 1) route event in correct streams based on tag -- This message was sent by Atlassian JIRA (v6.3.4#6332)