You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2016/06/25 16:54:37 UTC

[jira] [Updated] (BEAM-323) The InProcessPipelineRunner uses user objects for State and Timer lookups

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

Daniel Halperin updated BEAM-323:
---------------------------------
    Fix Version/s: 0.2.0-incubating

> The InProcessPipelineRunner uses user objects for State and Timer lookups
> -------------------------------------------------------------------------
>
>                 Key: BEAM-323
>                 URL: https://issues.apache.org/jira/browse/BEAM-323
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>            Priority: Critical
>             Fix For: 0.2.0-incubating
>
>
> The runner keys state based on the user key that it was grouped by, instead of the structural value of that key. This causes callbacks to be updated based on java equality, so an object with a poor equals can cause the Pipeline to not progress.
> Initially uncovered in https://github.com/apache/incubator-beam/pull/409



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