Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Thu, 29 May 2014 16:33:01 +0000 (UTC)
From: "Gabriel Reid (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12696921.1393250963576.39944.1401381181874@arcas>
In-Reply-To: <JIRA.12696921.1393250963576@arcas>
References: <JIRA.12696921.1393250963576@arcas>
Subject: [jira] [Commented] (CRUNCH-355) Rename jobs to show how many stages
 have done before job submission
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gabriel Reid commented on CRUNCH-355:
-------------------------------------

+1, looks good, especially that the job ID remains intact.

> Rename jobs to show how many stages have done before job submission
> -------------------------------------------------------------------
>
>                 Key: CRUNCH-355
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-355
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>            Reporter: Chao Shi
>            Assignee: Josh Wills
>         Attachments: CRUNCH-355.patch
>
>
> The naming mechanism introduced in CRUNCH-262 has a flaw. It adds (m/n) to the end of job name, where m is the current stage number at planning time and n is the total number of stages.
> Suppose in the following case, where A takes a long time to run, when B is submitted, C and D have completed. As there are 3 jobs done, we should expect B to be (4/5) rather than (2/5) or (3/5).
> {code}
> A   C
> |   |
> B   D
>  \ /
>   E
> {/code}
> In planning time, we don't have a clue which stage will complete earlier. So I think it better to assign it at runtime.
> One problem here is that the user may access to Job instance before it submits. So he may observe a sudden change of job name.


--
This message was sent by Atlassian JIRA
(v6.2#6252)