[jira] [Commented] (BEAM-11049) Elminate CreatePCollectionView pseudo-"primitive"

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257443#comment-17257443 ] 

Beam JIRA Bot commented on BEAM-11049:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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
>              Labels: Clarified, stale-assigned
>
> 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)