Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Wed, 11 Sep 2013 15:11:51 +0000 (UTC)
From: "Josh Wills (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12667079.1378374273045.116365.1378912311725@arcas>
In-Reply-To: <JIRA.12667079.1378374273045@arcas>
References: <JIRA.12667079.1378374273045@arcas>
Subject: [jira] [Commented] (CRUNCH-262) Crunch's job name is too long...
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Wills commented on CRUNCH-262:
-----------------------------------

+1
                
> Crunch's job name is too long...
> --------------------------------
>
>                 Key: CRUNCH-262
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-262
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Chao Shi
>         Attachments: crunch-262.patch, crunch-262-v2.patch, job-name-too-long-2.png, job-name-too-long.png
>
>
> Please check the screenshot of my very long named job. I think Hive is better on this: they put an ellipsis if job name is too long. We can also append "(n/m)" to it, where n is the current stage number and m is the total number of stages.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira