[
https://issues.apache.org/jira/browse/HIVE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127915#comment-14127915
]
Xuefu Zhang edited comment on HIVE-8017 at 9/10/14 1:51 AM:
------------------------------------------------------------
[~lirui] That depends on the query. If the query semantically doesn't guarantee
the order of the output, updating MR/Tez golden file should be okay. We know
MR, and possibly Tez give ordered the output even the query doesn't require it.
I guess this is the case for the test failures here.
It might make sense to create a trunk JIRA to address the MR/Tez golden files
changes. This would make future merge easier.
was (Author: xuefuz):
[~lirui] That depends on the query. If the query semantically doesn't guarantee
the order of the output, updating MR/Tez golden file should be okay. We know
MR, and possibly Tez give ordered the output even the query doesn't require it.
I guess this is the case for the test failures here.
> Use HiveKey instead of BytesWritable as key type of the pair RDD [Spark
> Branch]
> -------------------------------------------------------------------------------
>
> Key: HIVE-8017
> URL: https://issues.apache.org/jira/browse/HIVE-8017
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Reporter: Rui Li
> Assignee: Rui Li
> Attachments: HIVE-8017-spark.patch, HIVE-8017.2-spark.patch
>
>
> HiveKey should be used as the key type because it holds the hash code for
> partitioning. While BytesWritable serves partitioning well for simple cases,
> we have to use {{HiveKey.hashCode}} for more complicated ones, e.g. join,
> bucketed table, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
