[
https://issues.apache.org/jira/browse/BEAM-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298981#comment-17298981
]
Beam JIRA Bot commented on BEAM-11049:
--------------------------------------
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.
> 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
> Priority: P2
> Labels: Clarified, stale-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)
