beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BEAM-92) Data-dependent sinks
Date Thu, 30 Mar 2017 17:09:41 GMT

    [ https://issues.apache.org/jira/browse/BEAM-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949420#comment-15949420
] 

Daniel Halperin edited comment on BEAM-92 at 3/30/17 5:08 PM:
--------------------------------------------------------------

Progress:

* Data-dependent file based sink is in PR
* Data-dependent BigQuery sink is submitted

Experience over the past year makes us think that the Write/Sink transform is not general
and instead we'll need individual implementations that follow similar design patterns in spirit
but are hard to unify at a low level.

Self-assigning to clean up.


was (Author: dhalperi@google.com):
Progress:

* Data-dependent file based sink is in PR
* Data-dependent BigQuery sink is in PR

Experience over the past year makes us think that the Write/Sink transform is not general
and instead we'll need individual implementations that follow similar design patterns in spirit
but are hard to unify at a low level.

Self-assigning to clean up.

> Data-dependent sinks
> --------------------
>
>                 Key: BEAM-92
>                 URL: https://issues.apache.org/jira/browse/BEAM-92
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Eugene Kirpichov
>            Assignee: Daniel Halperin
>
> Current sink API writes all data to a single destination, but there are many use cases
where different pieces of data need to be routed to different destinations where the set of
destinations is data-dependent (so can't be implemented with a Partition transform).
> One internally discussed proposal was an API of the form:
> {code}
> PCollection<Void> PCollection<T>.apply(
>     Write.using(DoFn<T, SinkT> where,
>                 MapFn<SinkT, WriteOperation<WriteResultT, T>> how)
> {code}
> so an item T gets written to a destination (or multiple destinations) determined by "where";
and the writing strategy is determined by "how" that produces a WriteOperation (current API
- global init/write/global finalize hooks) for any given destination.
> This API also has other benefits:
> * allows the SinkT to be computed dynamically (in "where"), rather than specified at
pipeline construction time
> * removes the necessity for a Sink class entirely
> * is sequenceable w.r.t. downstream transforms (you can stick transforms onto the returned
PCollection<Void>, while the current Write.to() returns a PDone)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message