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

Chao commented on HIVE-8331:
----------------------------

Discussed with [~szehon] offline - we think for {{parallel_join0.q}} and 
{{parallel_join1.q}}, it's just a ordering problem,
and I think it's OK for MR and Spark to have different result order.
{{vectorized_shufflejoin.q}} and {{union22.q}} have same results but different 
plans as MR. I think they are good.
For {{union_remove_18.q}}, the unit test result is different from MR, and looks 
wrong to me. Interestingly, when I run the query in CLI spark mode, the result 
is the same as MR. I need to debug this.

> HIVE-8303 followup, investigate result diff [Spark Branch]
> ----------------------------------------------------------
>
>                 Key: HIVE-8331
>                 URL: https://issues.apache.org/jira/browse/HIVE-8331
>             Project: Hive
>          Issue Type: Task
>          Components: Spark
>            Reporter: Xuefu Zhang
>            Assignee: Chao
>
> HIVE-8303 patch introduced some result diffs for some spark tests. We need to 
> investigate those, including parallel_join0.q, union22.q, 
> vectorized_shufflejoin.q, union_remove_18.q, and maybe more.
> Also the investigation includes the test failures related to spark. 
> Specifically, union_remove_18.q demonstrated random order.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to