You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:07:19 UTC
[jira] [Commented] (BEAM-8804) PCollectionList support in
cross-language transforms
[ https://issues.apache.org/jira/browse/BEAM-8804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174589#comment-17174589 ]
Beam JIRA Bot commented on BEAM-8804:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> PCollectionList support in cross-language transforms
> ----------------------------------------------------
>
> Key: BEAM-8804
> URL: https://issues.apache.org/jira/browse/BEAM-8804
> Project: Beam
> Issue Type: Improvement
> Components: beam-model
> Reporter: Heejong Lee
> Priority: P2
> Labels: stale-P2
>
> Currently, Beam model doesn't have any information on the order of input/output PCollections from PTransforms. Therefore, PCollectionList needs to be converted to PCollectionTuple when it goes across the cross-language boundaries (or even in the same language, whenever it is converted between in-memory object and proto) and it's impossible to recreate PCollectionList from proto with the original order. The possible workaround is just to use PCollectionTuple with integer id (starting from 0 like indexes) instead of PCollectionList. In that case, we should first well-define how we generate proto from PCollectionList since each SDK uses a different convention.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)