[
https://issues.apache.org/jira/browse/BEAM-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212534#comment-17212534
]
Kenneth Knowles commented on BEAM-11049:
----------------------------------------
The title, component, and code attached to that ticket do not match:
- removing a primitive isn't part of the Java SDK, but the model
- the code only conditionally removes it, so it isn't resolved
I do hope this will finish the job and it will never appear in the proto again.
I do not know the status of other SDK's translations.
> Elminate CreatePCollectionView pseudo-"primitive"
> -------------------------------------------------
>
> Key: BEAM-11049
> URL: https://issues.apache.org/jira/browse/BEAM-11049
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: P2
>
> Currently each {{PCollectionView}} is "created" by a primitive
> {{CreatePCollectionView}} primitive in the Java SDK. This is an artifact of
> how runners translated the {{View}} transforms.
> But in portability (and actually before that) PCollectionView is just a POJO
> of metadata for how to read a PCollection as a side input. It is PValue to
> the Java SDK but in portability there is only one kind of value: PCollection.
> Runners should not depend on the exact expansion of the {{View}} transforms.
> Until they are all migrated off of it, the transform must be left in the
> expanion, so runners who are migrated off of it will need to remove it from
> their translation or insert a noop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
