beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbonofre <>
Subject [GitHub] incubator-beam pull request #1573: [BEAM-1127] Create an unique source when ...
Date Sat, 10 Dec 2016 16:20:49 GMT
GitHub user jbonofre opened a pull request:

    [BEAM-1127] Create an unique source when using a JMS topic to avoid p…

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

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

    $ git pull BEAM-1127

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 #1573
commit e3a1d73c53a51f1c9ce59c6f3ce2ba5fe6f54f65
Author: Jean-Baptiste Onofré <>
Date:   2016-12-10T16:19:44Z

    [BEAM-1127] Create an unique source when using a JMS topic to avoid potential messages


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