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

ASF GitHub Bot commented on SAMZA-1698:
---------------------------------------

GitHub user shanthoosh opened a pull request:

    https://github.com/apache/samza/pull/502

    SAMZA-1698: Update appStatus on failures in localApplication.run(streamApp).

    

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

    $ git pull https://github.com/shanthoosh/samza 
local_application_runner_set_exception_in_finish

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

    https://github.com/apache/samza/pull/502.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 #502
    
----
commit e6bf2a3734955f462a2b5a88addcb9ff46409832
Author: Shanthoosh Venkataraman <santhoshvenkat1988@...>
Date:   2018-05-02T21:37:02Z

    Fix LocalApplicationRunner status on exception.

----


> Update  appStatus on failures in localApplication.run(streamApp).
> -----------------------------------------------------------------
>
>                 Key: SAMZA-1698
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1698
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Shanthoosh Venkataraman
>            Assignee: Shanthoosh Venkataraman
>            Priority: Major
>
> In existing LocalApplicationRunner implementation, any exception in 
> localApplicationRunner.run(streamApp) is bubbled up to the caller without 
> updating the localApplicationRunner.appStatus.
> This leaves the localApplicationRunner object in a weird state. 
> Any monitoring reported based on applicationStatus will be incorrect.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to