falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1888) Falcon JMS Notification details and documentation
Date Thu, 14 Apr 2016 19:11:25 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241747#comment-15241747
] 

ASF GitHub Bot commented on FALCON-1888:
----------------------------------------

GitHub user vramachan opened a pull request:

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

    FALCON-1888 : Falcon JMS notification details and example

    Updates the operability document to enable Falcon user notifications and example code
to read and Map Message from ActiveMQ.

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

    $ git pull https://github.com/vramachan/falcon master

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

    https://github.com/apache/falcon/pull/101.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 #101
    
----
commit a886958640cfc9b4172aa050d566c472895583b9
Author: Venkatesan Ramachandran <vramachandran@hortonworks.com>
Date:   2016-03-16T19:23:40Z

    FALCON-1838:Export instances are not added graph db for lineage tracking

commit afa5173b0150cbf586a59b4b596872e5e8e37b5f
Author: Venkatesan Ramachandran <vramachandran@hortonworks.com>
Date:   2016-03-16T23:48:10Z

    FALCON-1838:Export instances are not added graph db for lineage tracking - remove call
to findVertex(), refactor method name

commit fac28b184191fc9710cf0abf8b89abb5bf8f6eed
Author: Venkatesan Ramachandran <vramachandran@hortonworks.com>
Date:   2016-04-12T23:16:31Z

    Merge

commit 3cfc4e02b3daea2c20d9c99532319c2f7515e96c
Author: Venkatesan Ramachandran <vramachandran@hortonworks.com>
Date:   2016-04-14T18:28:53Z

    FALCON-1888 : Falcon JMS details and usage

commit a1fe26e1f0925dd2106efe307a8ae32ba75f7d0e
Author: Venkatesan Ramachandran <vramachandran@hortonworks.com>
Date:   2016-04-14T19:07:47Z

    git rebase from upstream master to ramachan fork master

----


> Falcon JMS Notification details and documentation
> -------------------------------------------------
>
>                 Key: FALCON-1888
>                 URL: https://issues.apache.org/jira/browse/FALCON-1888
>             Project: Falcon
>          Issue Type: Bug
>          Components: general
>    Affects Versions: trunk
>            Reporter: Venkatesan Ramachandran
>            Assignee: Venkatesan Ramachandran
>
> Falcon JMS notification documentation here - https://falcon.apache.org/Operability.html
specifies there will be a topic per Feed and Process. 
> But looking at an running Falcon instance, all the notifications are published to FALCON.ENTITY.TOPIC
but nothing to Feed/Process specific Topics.
> 1) Double check the topic names where the JMS notification gets published.
> 2) Document the JMS message format
> 3) Sample to read the messages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message