Details
-
Bug
-
Status: Triage Needed
-
P3
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The Python SDK currently ignores any tags set on PCollections manually when applying PTransforms when adding the PCollection to the PTransform outputs. In the add_output method, the tag is set to None for all PValues, meaning the output tags are set to an enumeration index over the PCollection outputs. The tags are not propagated to correctly which can be a problem on relying on the output PCollection tags to match the user set values.
The fix is to correct BEAM-1833, and always pass in the tags. However, that doesn't fix the problem for nested PCollections. If you have a dict of lists of PCollections, what should their tags be correctly set to? In order to fix this, first propagate the correct tag then talk with the community about the best auto-generated tags.
Some users may rely on the old implementation, so a flag will be created: "force_generated_pcollection_output_ids" and be default set to False. If True, this will go to the old implementation and generate tags for PCollections.
Attachments
Issue Links
- is caused by
-
BEAM-1833 Restructure Python pipeline construction to better follow the Runner API
-
- Triage Needed
-
- links to
