[
https://issues.apache.org/jira/browse/MAPREDUCE-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550067#comment-14550067
]
Tsuyoshi Ozawa commented on MAPREDUCE-6298:
-------------------------------------------
{quote}
1. Usage of StringBuffer is discouraged as it's slower than StringBuilder.
{quote}
I thought it's better use StringBuilder rather than using + concatenation for
this case. What do you think?
http://blog.eyallupu.com/2010/09/under-hood-of-java-strings.html
{quote}
Do you want me to add another one similar to the existing one for RUNNING?
{quote}
Yes, you're right. I think we need to add the test for the backward
compatibility.
> Job#toString throws an exception when not in state RUNNING
> ----------------------------------------------------------
>
> Key: MAPREDUCE-6298
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6298
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Lars Francke
> Assignee: Lars Francke
> Priority: Minor
> Labels: BB2015-05-TBR
> Attachments: MAPREDUCE-6298.1.patch, MAPREDUCE-6298.2.patch,
> MAPREDUCE-6298.3.patch
>
>
> Job#toString calls {{ensureState(JobState.RUNNING);}} as the very first
> thing. That method causes an Exception to be thrown which is not nice.
> One thing this breaks is usage of Job on the Scala (e.g. Spark) REPL as that
> calls toString after every invocation and that fails every time.
> I'll attach a patch that checks state and if it's RUNNING prints the original
> message and if not prints something else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
