beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Cwik (JIRA)" <>
Subject [jira] [Commented] (BEAM-1348) Model the Fn Api
Date Thu, 18 May 2017 22:47:04 GMT


Luke Cwik commented on BEAM-1348:

Beam Fn API overview: 

And for those of you who have been following this thread and contributors focusing on Runner
integration with Apache Beam:
* How to process a bundle:
* How to send and receive data:

If you want to dive deeper, you should look at:
* Runner API Protobuf:
* Fn API Protobuf:
* Java SDK Harness:
* Python SDK Harness:

Next I'm planning on talking about Beam Fn State API and will need help from Runner contributors
to talk about caching semantics and key spaces and whether the integrations mesh well with
current Runner implementations. The State API is meant to support user state, side inputs,
and re-iteration for large values produced by GroupByKey.

> Model the Fn Api
> ----------------
>                 Key: BEAM-1348
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model-fn-api
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
> Create a proto representation of the services and data types required to execute the
Fn Api.

This message was sent by Atlassian JIRA

View raw message