schizophrenicmaniac commented on PR #40380:
URL: https://github.com/apache/beam/pull/40380#issuecomment-5946746632
@developer-rpai I don't think anything reaches it with more than one. ParDo
only takes a single PCollection: applying it to the pipeline/PBegin is rejected
at apply time in `Pipeline.apply` ("expects a PCollection as input"), and a
tuple of PCollections fails in `ParDo.expand`, both before translation.
`_named_inputs` puts that one main input first and the `python_side_input<N>`
tags after it. After a proto round trip, `AppliedPTransform.from_runner_api`
rebuilds `main_inputs` the same way, by dropping the side input tags listed in
the ParDoPayload. So every tag having the prefix can't really happen for a
stateful ParDo. If it somehow did, I'd rather it fail there than quietly take a
side input's coder like before.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
