You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Suhas Vasu (JIRA)" <ji...@apache.org> on 2014/11/06 10:31:34 UTC

[jira] [Closed] (FALCON-813) Expose job id for running jobs in Falcon

     [ https://issues.apache.org/jira/browse/FALCON-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suhas Vasu closed FALCON-813.
-----------------------------

Merged to trunk. Have validated the patch before merging.

> 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-v4.patch, FALCON-813-v5.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)