You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by PramodSSImmaneni <gi...@git.apache.org> on 2017/03/18 23:20:52 UTC

[GitHub] apex-core pull request #488: APEXCORE-641 Preventing a scenario where more t...

GitHub user PramodSSImmaneni opened a pull request:

    https://github.com/apache/apex-core/pull/488

    APEXCORE-641 Preventing a scenario where more than one the subscribe notification task can be scheduled simultaneously

    @vrozov please see. I missed this, something didnt feel right.

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

    $ git pull https://github.com/PramodSSImmaneni/apex-core APEXCORE-641

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

    https://github.com/apache/apex-core/pull/488.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 #488
    
----
commit c814ba6c9ec58a67dbce0e0fdcb88db607669bfc
Author: Pramod Immaneni <pr...@datatorrent.com>
Date:   2017-03-18T23:08:04Z

    APEXCORE-641 Preventing a scenario where more than one the subscriber notification task can be scheduled simultaneously

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---