falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-813) Expose job id for running jobs in Falcon
Date Mon, 20 Oct 2014 10:58:34 GMT

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

Shwetha G S commented on FALCON-813:
------------------------------------

{code}
+            if ((wfActionType.equalsIgnoreCase("pig") || wfActionType.equalsIgnoreCase("hive"))
+                    || (!wfActionType.startsWith(":") && !Status.SUCCEEDED.toString().equals(action.getExternalStatus())
+                    && !("-").equals(action.getExternalId()))) {
{code}
Can we just check the action name(pre-processing and post-processing) and status? That will
be simple

{code}
+                InstancesResult.InstanceAction instanceAction =
+                        new InstancesResult.InstanceAction(action.getId().split("@")[1],
action.getExternalStatus(),
+                                action.getConsoleUrl());
{code}
Use action name and status instead

{code}
+                    if (!subWfAction.getType().startsWith(":") && !subWfAction.getExternalId().equals("-"))
{
{code}
Use just the type as all meta nodes start, end, fork and join will have :

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

Mime
View raw message