[
https://issues.apache.org/jira/browse/BEAM-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121914#comment-17121914
]
Kenneth Knowles commented on BEAM-8140:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Python API: PTransform should be immutable and reusable
> -------------------------------------------------------
>
> Key: BEAM-8140
> URL: https://issues.apache.org/jira/browse/BEAM-8140
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Chris Suchanek
> Assignee: Robert Bradshaw
> Priority: P2
> Labels: stale-assigned
>
> While the Java API seems fine the Python API is (at least) counterintuitive.
> Let's see the following example:
> {code:python}
> p1 = beam.Pipeline()
> p2 = beam.Pipeline()
> node = 'ReadTrainData' >> beam.io.ReadFromText("/tmp/aaa.txt")
> p1 | node
> p2 | node //fails here {code}
> The code above will fail because the _node_ somehow remembers that it was
> already attached to _p1_. In fact, unlike in Java, the | (apply) method is
> defined on the _PTransform_.
> If any, only the pipeline object should be mutable here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
