[
https://issues.apache.org/jira/browse/MAPREDUCE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787431#action_12787431
]
Hadoop QA commented on MAPREDUCE-1097:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12427297/MAPREDUCE-1097-2.patch
against trunk revision 888269.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 new or modified tests.
+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 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/173/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/173/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/173/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h3.grid.sp2.yahoo.net/173/console
This message is automatically generated.
> Changes/fixes to support Vertica 3.5
> ------------------------------------
>
> Key: MAPREDUCE-1097
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1097
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.21.0
> Environment: Hadoop 0.21.0 pre-release and Vertica 3.5
> Reporter: Omer Trajman
> Assignee: Omer Trajman
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1097-2.patch, MAPREDUCE-1097.patch
>
>
> Vertica 3.5 includes three changes that the formatters should handle:
> 1) deploy_design function that handles much of the logic in the optimize
> method. This improvement uses deploy_design if the server version supports
> it instead of orchestrating in the formatter function.
> 2) truncate table instead of recreating the table
> 3) numeric, decimal, money, number types (all the same path)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
