[
https://issues.apache.org/jira/browse/FALCON-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194450#comment-14194450
]
Shwetha G S commented on FALCON-813:
------------------------------------
{code}
+ if (action.getType().equalsIgnoreCase("sub-workflow")) {
+ List<WorkflowAction> subWorkFlowActions =
getWorkflowInfo(cluster, action.getExternalId()).getActions();
{code}
Handle null for action.getExternalId().
Currently, job info is returned for all APIs. But should be returned only for
status. Doesn't make sense to fetch for rerun, kill etc. Can you take care of
it?
> Expose job id for running jobs in Falcon
> ----------------------------------------
>
> Key: FALCON-813
> URL: https://issues.apache.org/jira/browse/FALCON-813
> Project: Falcon
> Issue Type: Improvement
> Components: client
> Reporter: Suhas Vasu
> Assignee: Suhas Vasu
> Attachments: FALCON-813-v2.patch, FALCON-813-v3.patch,
> FALCON-813.patch
>
>
> Currently we have no way of tracking a running job via Falcon.
> Suppose we wanna look at the task logs of a particular job, we have to use
> {{-logs}} option via CLI. This option gives us the link of the logs after it
> has been copied to staging directory. The logMover might fail and we may not
> get these logs.
> Also there is no way of checking the logs of running jobs via this option.
> Hence it would be really helpful if we expose the job url through CLI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
