You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Thomas Groh (JIRA)" <ji...@apache.org> on 2017/06/09 18:42:18 UTC
[jira] [Resolved] (BEAM-2364) PCollectionView should not be a
PValue, it should expand to its underlying PCollection
[ https://issues.apache.org/jira/browse/BEAM-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Groh resolved BEAM-2364.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
The expansion of PCollectionView has changed to be a PCollection, and Transform Hierarchy now fully expands all values until it only has PCollections. There can be some cleanup work done, but (in order to not break any custom POutputs) this is effectively complete.
> PCollectionView should not be a PValue, it should expand to its underlying PCollection
> --------------------------------------------------------------------------------------
>
> Key: BEAM-2364
> URL: https://issues.apache.org/jira/browse/BEAM-2364
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Assignee: Thomas Groh
> Labels: backward-incompatible
> Fix For: 2.1.0
>
>
> This bug has been present for a very long time.
> It is a change to {{@Internal}} details but is going to be backwards-incompatible in a couple ways there, because backwards compatible behavior is incorrect. But we need to be very careful with the surrounding logic.
> The particular motivating need is that as long as a PCollectionView expands to only itself, the outputs for surgery and serialization are not correct. There may be a solution involving hardcoded logic, TBD.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)