beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-647) Fault-tolerant sideInputs via Broadcast variables
Date Thu, 15 Dec 2016 17:51:59 GMT


ASF GitHub Bot commented on BEAM-647:

GitHub user kobisalant opened a pull request:

    [BEAM-647] Fault-tolerant sideInputs via Broadcast variables

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

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

    $ git pull BEAM-647-Fault-tolerant-sideInputs

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

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

    This closes #1624
commit 228c613c70c4edf1b01294a487d49f0a5492136e
Author: ksalant <>
Date:   2016-12-15T17:42:47Z

    [BEAM-647] Fault-tolerant sideInputs via Broadcast variables


> Fault-tolerant sideInputs via Broadcast variables
> -------------------------------------------------
>                 Key: BEAM-647
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Amit Sela
>            Assignee: Kobi Salant
> Following which enables checkpointing
to recover from failures, sideInputs (being implemented by broadcast variables) should be
handled in a specific manner as described here:
> This is a bit more complicated than Aggregators (via Accumulators) as they are implemented
using a single "aggregating"  Accumulator, while a pipeline may contain multiple sideInputs.

This message was sent by Atlassian JIRA

View raw message