GitHub user tgroh opened a pull request:

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

    Make TimerData#compareTo consistent with equals

    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](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    Timers are equal if the domain, timestamp, and namespace are equal.
    Compare these values in compareTo. The ordering of TimerData that are
    not in the same namespace or domain is arbitrary.

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

    $ git pull https://github.com/tgroh/incubator-beam timers_compare_to

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

    https://github.com/apache/incubator-beam/pull/813.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 #813
    
----
commit 9fe6ce22ca12b48704deb0e7cf3c583dff9b1870
Author: Thomas Groh <[email protected]>
Date:   2016-08-10T20:52:14Z

    Make TimerData#compareTo consistent with equals
    
    Timers are equal if the domain, timestamp, and namespace are equal.
    Compare these values in compareTo. The ordering of TimerData that are
    not in the same namespace or domain is arbitrary.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to