[jira] [Updated] (STORM-18) Trident sections connected by a merge should not be required to enforce equal parallelisms

["Rick Kellogg (JIRA)" <ji...@apache.org>]

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

Rick Kellogg updated STORM-18:
------------------------------
    Component/s: storm-core

> Trident sections connected by a merge should not be required to enforce equal parallelisms
> ------------------------------------------------------------------------------------------
>
>                 Key: STORM-18
>                 URL: https://issues.apache.org/jira/browse/STORM-18
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: James Xu
>
> https://github.com/nathanmarz/storm/issues/322
> Currently, Trident enforces that partitionings are consistent, so that when Trident is forced to split up two pieces into separate bolts, an identity partitioning is used and the parallelism of the two parts must be identical. Enforcing this isn't necessary in a merge and in fact just makes it harder to have separate parallelisms for the different pieces.
> A current workaround is to manually set the partitioning to separate the pieces (like with a shuffle partitioning).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)