You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Heejong Lee (Jira)" <ji...@apache.org> on 2019/12/27 01:30:00 UTC
[jira] [Resolved] (BEAM-8905) matching Java PCollectionTuple
translation naming convention in expansion service with index only
[ https://issues.apache.org/jira/browse/BEAM-8905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Heejong Lee resolved BEAM-8905.
-------------------------------
Fix Version/s: 2.18.0
Resolution: Fixed
> matching Java PCollectionTuple translation naming convention in expansion service with index only
> -------------------------------------------------------------------------------------------------
>
> Key: BEAM-8905
> URL: https://issues.apache.org/jira/browse/BEAM-8905
> Project: Beam
> Issue Type: Improvement
> Components: java-fn-execution
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Python PCollectionTuple is translated to an index-keyed map e.g. \{0->pcollection1, 1->pcollection2}, however Java PCollectionTuple is translated to slightly different formats such as \{output_0->pcollection1, output_1->pcollection2}. We need to match these naming conventions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)