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-2051) Falcon post-processing services are not getting invoked
Date Thu, 30 Jun 2016 00:58:12 GMT

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

ASF GitHub Bot commented on FALCON-2051:

GitHub user vramachan opened a pull request:


    FALCON-2051 : PostProcessing needs to send JMS message so that REPL m…

    Basically, reverted the FALCON-1926 changes. 
    We will attempt to solve it properly by not sending JMS message from Falcon PostProcessing
after 0.10 release.

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

    $ git pull https://github.com/vramachan/falcon FALCON-2051.PostProcessingNotInvoked.0.10

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 #201
commit c0b9b4d1ce6036818acf5951bd17017b16f988f6
Author: Venkatesan Ramachandran <vramachandran@hortonworks.com>
Date:   2016-06-30T00:34:21Z

    FALCON-2051 : PostProcessing needs to send JMS message so that REPL metrics can be added
to the GraphDB


> Falcon post-processing services are not getting invoked
> -------------------------------------------------------
>                 Key: FALCON-2051
>                 URL: https://issues.apache.org/jira/browse/FALCON-2051
>             Project: Falcon
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 0.9
>            Reporter: Peeyush Bishnoi
>            Assignee: Venkatesan Ramachandran
>            Priority: Blocker
>             Fix For: 0.10
> With latest Falcon, none of the post-processing services like metadata, late data handling,
retry is getting invoked. Hence created a blocker issue to fix this.

This message was sent by Atlassian JIRA

View raw message