You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/04/19 21:39:41 UTC

[jira] [Resolved] (BEAM-1933) Revisit Runner API PCollection unique_name

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

Kenneth Knowles resolved BEAM-1933.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Not applicable

> Revisit Runner API PCollection unique_name
> ------------------------------------------
>
>                 Key: BEAM-1933
>                 URL: https://issues.apache.org/jira/browse/BEAM-1933
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-model-runner-api, sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Kenneth Knowles
>            Priority: Minor
>             Fix For: Not applicable
>
>
> The Java SDK performs no work to ensure that a PCollection has a unique name. Most names will end up being unique, because they are autogenerated based on the full name of the producing transform, but names can be set by users arbitrarily.
> We can generate a unique name, potentially one based on the PCollection name, but this may not map to something that is "stable over multiple evolutions of a pipeline"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)