You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Deepak Marathe (JIRA)" <ji...@apache.org> on 2014/02/05 12:18:10 UTC

[jira] [Comment Edited] (FALCON-299) Falcon to return job tracker URLs for the instances of the process specified

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

Deepak Marathe edited comment on FALCON-299 at 2/5/14 11:17 AM:
----------------------------------------------------------------

im going to work upon it

Pain point : multiple level of indirections needed to obtain the jobtracker url, using falcon and then oozie.

The objective : To be able to obtain the jt url in a single go ( ofcourse after resolving the instanceid of the interested process in the previous step)

Approach to solution : as per [~shwethags], this would translate to a new api which would accept an instance-id of the process and return the details for the workflow, subworkflow and all the individual actions in the user-workflow.




was (Author: deepak.marathe):
im going to work upon it
approach : as per [~shwethags], this would translate to a new api which would accept an instanceid of the process and return the details for the subworkflows and all the individual actions in the userworkflow.


> Falcon to return job tracker URLs for the instances of the process specified 
> -----------------------------------------------------------------------------
>
>                 Key: FALCON-299
>                 URL: https://issues.apache.org/jira/browse/FALCON-299
>             Project: Falcon
>          Issue Type: New Feature
>          Components: client, process
>    Affects Versions: 0.5
>            Reporter: Deepak Marathe
>              Labels: feature
>             Fix For: 0.5
>
>
> falcon status command does not return the jobtracker url for the process instances which have either run or are in running state.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)