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

Pallavi Rao commented on FALCON-1674:
-------------------------------------

IMO, since falcon will be absorbing some of the co-ordinator features, the 
status list will grow (more than what plain oozie workflow supports). If we map 
it a Oozie workflow status, we'll be providing wrong information to the user.

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

Reply via email to