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

Remus Rusanu commented on HIVE-6449:
------------------------------------

Fixed by adding Derby jar into the CLASSPATH, right there in hadoop.cmd. Just 
one more hack to get .q tests to run on Windows... I wish the whole 
pom->surefire->driver->hadoopCLI->task chain would work correctly vis-a-vis 
execution on a Windows environment, but is beyond my bandwith to fix it now. 
I'm explaining my hack fix for the unfortunate soul running into this later... 
and that includes myself 2 months later when I forgot what I did.

> EXPLAIN has diffs in Statistics in tests generated on Windows vs. test 
> generated on Linux
> -----------------------------------------------------------------------------------------
>
>                 Key: HIVE-6449
>                 URL: https://issues.apache.org/jira/browse/HIVE-6449
>             Project: Hive
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Remus Rusanu
>            Assignee: Remus Rusanu
>            Priority: Critical
>
> When .q.out files are generated on Windows the statistics in EXPLAIN differ 
> from ones generated on Linux. Eg:
> {code}
> Running: diff -a 
> /root/hive/itests/qtest/../../itests/qtest/target/qfile-results/clientpositive/vectorized_parquet.q.out
>  
> /root/hive/itests/qtest/../../ql/src/test/results/clientpositive/vectorized_parquet.q.out
> 72c72
> <             Statistics: Num rows: 12288 Data size: 73728 Basic stats: 
> COMPLETE Column stats: NONE
> ---
> >             Statistics: Num rows: 2072 Data size: 257046 Basic stats: 
> > COMPLETE Column stats: NONE
> 75c75
> <               Statistics: Num rows: 6144 Data size: 36864 Basic stats: 
> COMPLETE Column stats: NONE
> ---
> >               Statistics: Num rows: 1036 Data size: 128523 Basic stats: 
> > COMPLETE Column stats: NONE
> {code}



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

Reply via email to