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

Xuefu Zhang commented on HIVE-3688:
-----------------------------------

I'm not sure if generating different sets of output file is the best approach 
to address the issue. It can become unmanageable if the number of dimensions 
rises. Right now, we have jvm version, hadoop version, etc. Image down the road 
we have JDK8.

I would think it's better for hive to generate more deterministic result which 
doesn't vary with JVM version. For instance, we can order the output of "show 
grant" so that the set of the privileges returned doesn't vary in 
order(HIVE-4858).
                
> Various tests failing in TestNegativeCliDriver, TestParseNegative, TestParse 
> when using JDK7
> --------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3688
>                 URL: https://issues.apache.org/jira/browse/HIVE-3688
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor, Tests
>    Affects Versions: 0.9.1, 0.10.0
>            Reporter: Chris Drome
>            Assignee: Chris Drome
>         Attachments: HIVE-3688-0.9.patch, HIVE-3688-trunk.patch
>
>
> The following tests are failing when using JDK7.
> TestNegativeCliDriver:
> case_sensitivity.q
> cast1.q
> groupby1.q
> groupby2.q
> groupby3.q
> groupby4.q
> groupby5.q
> groupby6.q
> input1.q
> input2.q
> input20.q
> input3.q
> input4.q
> input5.q
> input6.q
> input7.q
> input8.q
> input9.q
> input_part1.q
> input_testsequencefile.q
> input_testxpath.q
> input_testxpath2.q
> join1.q
> join2.q
> join3.q
> join4.q
> join5.q
> join6.q
> join7.q
> join8.q
> sample1.q
> sample2.q
> sample3.q
> sample4.q
> sample5.q
> sample6.q
> sample7.q
> subq.q
> udf1.q
> udf4.q
> udf6.q
> udf_case.q
> udf_when.q
> union.q
> TestParseNegative:
> invalid_function_param2.q
> TestNegativeCliDriver:
> fs_default_name1.q.out_0.23_1.7
> fs_default_name2.q.out_0.23_1.7
> invalid_cast_from_binary_1.q.out_0.23_1.7
> invalid_cast_from_binary_2.q.out_0.23_1.7
> invalid_cast_from_binary_3.q.out_0.23_1.7
> invalid_cast_from_binary_4.q.out_0.23_1.7
> invalid_cast_from_binary_5.q.out_0.23_1.7
> invalid_cast_from_binary_6.q.out_0.23_1.7
> wrong_column_type.q.out_0.23_1.7

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to