beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tgroh <>
Subject [GitHub] incubator-beam pull request: [BEAM-22] Use an AtomicReference in I...
Date Tue, 10 May 2016 20:29:15 GMT
GitHub user tgroh opened a pull request:

    [BEAM-22] Use an AtomicReference in InProcessSideInputContainer

    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](
    This fixes a TOCTOU race in the contents updating logic, where the
    determination that the current pane should replace the contents of the
    side input and the replacement is not a single atomic operation. Using
    AtomicReference allows the use of compareAndSet to ensure that the
    replacement can only occur on the pane that the decision to replace was
    made with.
    Fixes a race where a pane could be the latest, and replace a
    pane, but would be lost due to an earlier pane being written between the
    invalidation and loading of contents.
    Fixes a race where a reader can incorrectly read an empty iterable as
    the contents of a PCollectionView, due to occuring between the
    invalidate and reload steps.

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

    $ git pull atomic_reference_side_input_container

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 #318


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message