[
https://issues.apache.org/jira/browse/BEAM-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266057#comment-16266057
]
ASF GitHub Bot commented on BEAM-3243:
--------------------------------------
jkff commented on issue #4172: [BEAM-3243] support multiple anonymous classes
from the same enclosing class in a pipeline
URL: https://github.com/apache/beam/pull/4172#issuecomment-347018533
Using multiple anonymous DoFn's with the same enclosing class within the
same composite transform is already possible if you specify the transform name
in .apply() - e.g.: .apply("Something", ParDo.of(new DoFn..)).apply("Something
else", ParDo.of(new DoFn..)). This is a good thing rather than a bug, because
using generated names like `Enclosing$1` is unstable w.r.t. pipeline update:
any reordering of the anonymous classes, or adding a new one, or making an
existing one be non-anonymous, will change the numbering and make the pipeline
update-incompatible.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> multiple anonymous DoFn lead to conflicting names
> -------------------------------------------------
>
> Key: BEAM-3243
> URL: https://issues.apache.org/jira/browse/BEAM-3243
> Project: Beam
> Issue Type: Task
> Components: sdk-java-core
> Reporter: Romain Manni-Bucau
> Assignee: Romain Manni-Bucau
> Fix For: 2.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
