You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/06 20:08:59 UTC
[jira] [Commented] (BEAM-1198) ViewFn: explicitly decouple runner
materialization of side inputs from SDK-specific mapping
[ https://issues.apache.org/jira/browse/BEAM-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15805610#comment-15805610 ]
ASF GitHub Bot commented on BEAM-1198:
--------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/beam/pull/1678
> ViewFn: explicitly decouple runner materialization of side inputs from SDK-specific mapping
> -------------------------------------------------------------------------------------------
>
> Key: BEAM-1198
> URL: https://issues.apache.org/jira/browse/BEAM-1198
> Project: Beam
> Issue Type: New Feature
> Components: beam-model-fn-api, beam-model-runner-api
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
>
> For side inputs, the field {{PCollectionView.fromIterableInternal}} implies an "iterable" materialization of the contents of a PCollection, which is adapted to the desired user-facing type within a UDF (today the PCollectionView "is" the UDF)
> In practice, runners get adequate performance by special casing just a couple of types of PCollectionView in a rather cumbersome manner.
> The design to improve this is https://s.apache.org/beam-side-inputs-1-pager and this makes the de facto standard approach the actual model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)