beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-65) SplittableDoFn
Date Sat, 27 Aug 2016 01:53:20 GMT

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

ASF GitHub Bot commented on BEAM-65:
------------------------------------

GitHub user jkff opened a pull request:

    https://github.com/apache/incubator-beam/pull/896

    [BEAM-65] SplittableDoFn prototype.

    Work in progress. Currently only runs in direct runner,
    and not ready for any use by real users.
    
    No tests for most of the code yet (will add later in this PR) but the rest is ready to
take a look.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jkff/incubator-beam splittable-do-fn

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-beam/pull/896.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #896
    
----
commit f025018ec24f7b795886aee58c4df689f87a6481
Author: Eugene Kirpichov <kirpichov@google.com>
Date:   2016-08-12T00:13:53Z

    [BEAM-65] SplittableDoFn prototype.
    
    Work in progress. Currently only runs in direct runner,
    and not ready for any use by real users.

----


> SplittableDoFn
> --------------
>
>                 Key: BEAM-65
>                 URL: https://issues.apache.org/jira/browse/BEAM-65
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model
>            Reporter: Daniel Halperin
>            Assignee: Eugene Kirpichov
>            Priority: Minor
>
> SplittableDoFn is a proposed enhancement for "dynamically splittable work" to the Beam
model.
> Among other things, it would allow a unified implementation of bounded/unbounded sources
with dynamic work rebalancing and the ability to express multiple scalable steps (e.g., global
expansion -> file sizing & parsing -> splitting files into independently-processable
blocks) via composition rather than inheritance.
> This would make it much easier to implement many types of sources, to modify and reuse
existing sources. Also, it would improve scalability of the Beam model by moving things like
splitting a source from the control plane (where it is today -- glob -> List<FileBasedSource>
sent over service APIs) into the data plane (PCollection<Glob> -> PCollection<FileName>
-> ...).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message