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

Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2016/01/04 13:05:39 UTC

[jira] [Commented] (FALCON-1674) Fix the mapping of InstanceState status to workflow Status in InstancesResult

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

Ajay Yadava commented on FALCON-1674:
-------------------------------------

[~pallavi.rao] I suspect that the status returned are different for native scheduler and oozie under certain conditions e.g. READY/ WAITING. I had in my mind a consistent result for similar kind of scenarios across Native and Oozie. 

> Fix the mapping of InstanceState status to workflow Status in InstancesResult
> -----------------------------------------------------------------------------
>
>                 Key: FALCON-1674
>                 URL: https://issues.apache.org/jira/browse/FALCON-1674
>             Project: Falcon
>          Issue Type: Bug
>          Components: scheduler
>            Reporter: pavan kumar kolamuri
>            Assignee: Pallavi Rao
>            Priority: Blocker
>             Fix For: 0.9
>
>         Attachments: FALCON-1674.patch
>
>
> Ready status was added to workflow status in InstancesResult , which was not valid in case of oozie. We should fix mapping and remove this state.



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