beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BEAM-1198) ViewFn: explicitly decouple runner materialization of side inputs from SDK-specific mapping
Date Thu, 23 Mar 2017 04:57:41 GMT

     [ https://issues.apache.org/jira/browse/BEAM-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kenneth Knowles resolved BEAM-1198.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: First stable release
                   Not applicable

In the guts of things, this is now somewhat implemented, and the Runner / Fn API makes it
explicit and mandatory. No longer need to track IMO.

> 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
>             Fix For: Not applicable, First stable release
>
>
> 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.15#6346)

Mime
View raw message