[
https://issues.apache.org/jira/browse/HADOOP-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704622#action_12704622
]
Hadoop QA commented on HADOOP-5727:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12406649/03_id-noallocate.patch
against trunk revision 770044.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/264/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/264/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/264/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/264/console
This message is automatically generated.
> Faster, simpler id.hashCode() which does not allocate memory
> ------------------------------------------------------------
>
> Key: HADOOP-5727
> URL: https://issues.apache.org/jira/browse/HADOOP-5727
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Shevek
> Assignee: Shevek
> Attachments: 00_id-noallocate.patch, 03_id-noallocate.patch
>
>
> Integer.valueOf allocates memory if the integer is not in the object-cache,
> which is the vast majority of cases for the task id. It is possible to
> compute the hash code of an integer without going via the integer cache, and
> hence avoiding allocating memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
