[ https://issues.apache.org/jira/browse/CRUNCH-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760228#comment-13760228
]
Josh Wills commented on CRUNCH-262:
-----------------------------------
+1. You could put the length limit parameter into the o.a.c.impl.mr.plan.PlanningParameters
class, if you're so inclined.
> 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, 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
|