You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by yzheng-hortonworks <gi...@git.apache.org> on 2016/02/18 23:42:50 UTC

[GitHub] falcon pull request: FALCON-1111 Instance update on titan DB based...

GitHub user yzheng-hortonworks opened a pull request:

    https://github.com/apache/falcon/pull/47

    FALCON-1111 Instance update on titan DB based on JMS notifications on workflow jobs

    Add running, succeeded, failed, and suspended instances to titan DB based on JMS notifications on workflow jobs. Instance-entity edge properties (e.g. nominal time, status) are also added for vertex-centric indexing.

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

    $ git pull https://github.com/yzheng-hortonworks/falcon FALCON-1111

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

    https://github.com/apache/falcon/pull/47.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 #47
    
----
commit b76f64237c2de1d7be25a03253f692143fbd0d96
Author: yzheng-hortonworks <yz...@hortonworks.com>
Date:   2016-02-12T06:23:05Z

    FALCON-1111 Instance update on titan DB based on JMS notifications on workflow jobs

----


---
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.
---

[GitHub] falcon pull request: FALCON-1111 Instance update on titan DB based...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/falcon/pull/47


---
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.
---