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

Hive QA commented on HIVE-6105:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12621723/HIVE-6105.1.patch

{color:green}SUCCESS:{color} +1 4881 tests passed

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/819/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/819/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12621723

> LongWritable.compareTo needs shimming
> -------------------------------------
>
>                 Key: HIVE-6105
>                 URL: https://issues.apache.org/jira/browse/HIVE-6105
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Gunther Hagleitner
>            Assignee: Navis
>         Attachments: HIVE-6105.1.patch, HIVE-6105.1.patch.txt
>
>
> Compiled hive against hadoop-2. Running tests on hadoop 1 gives:
> Caused by: java.lang.NoSuchMethodError: 
> org.apache.hadoop.io.LongWritable.compareTo(Lorg/apache/hadoop/io/LongWritable;)I
>       at 
> org.apache.hadoop.hive.ql.udf.UDAFPercentile$MyComparator.compare(UDAFPercentile.java:62)
>       at 
> org.apache.hadoop.hive.ql.udf.UDAFPercentile$MyComparator.compare(UDAFPercentile.java:58)
>       at java.util.Arrays.mergeSort(Arrays.java:1270)
>       at java.util.Arrays.sort(Arrays.java:1210)
>       at java.util.Collections.sort(Collections.java:157)
>       at 
> org.apache.hadoop.hive.ql.udf.UDAFPercentile$PercentileLongEvaluator.terminate(UDAFPercentile.java:194)
>       ... 20 more
> I think the problem is that the compareTo function has changed from using 
> Object to using LongWritable as an argument. Seems this needs a shim. 
> However, we should also make sure that this shim doesn't hit performance too 
> hard.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to