beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertwb <>
Subject [GitHub] incubator-beam pull request #1274: Implement key range tracker.
Date Thu, 03 Nov 2016 20:01:13 GMT
GitHub user robertwb opened a pull request:

    Implement key range tracker.

    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 will be useful for Bigtable and other key-based sources.

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

    $ git pull key-range-tracker

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 #1274
commit 92deaac998b73d9d731b11f51fc20487ee0641a5
Author: Robert Bradshaw <>
Date:   2016-11-01T06:19:34Z

    Implement key range tracker.
    This will be useful for Bigtable and other key-based sources.


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