You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Chao (JIRA)" <ji...@apache.org> on 2014/10/24 20:00:34 UTC

[jira] [Updated] (HIVE-8533) Enable all q-tests for multi-insertion [Spark Branch]

     [ https://issues.apache.org/jira/browse/HIVE-8533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chao updated HIVE-8533:
-----------------------
    Attachment: HIVE-8533.1-spark.patch

Spark tests enabled in this patch:
{noformat}
auto_smb_mapjoin_14.q
groupby10.q
groupby11.q
groupby3_map_skew.q
groupby7.q
groupby7_noskew_multi_single_reducer.q
groupby8.q
groupby8_map.q
groupby8_map_skew.q
groupby8_noskew.q
groupby9.q
groupby_complex_types.q
groupby_complex_types_multi_single_reducer.q
groupby_multi_insert_common_distinct.q
pcr.q
smb_mapjoin_13.q
smb_mapjoin_15.q
smb_mapjoin_16.q
table_access_keys_stats.q
{noformat}

The result for {{groupby_complex_types_multi_single_reducer.q}} is different from MR's, but this is because it uses {{limit 10}}.

The result for {{groupby3_map_skew.q}} also is slightly different:
{noformat}
< 130091.0      260.182 256.10355987055016      98.0    0.0     142.92680950752379      143.06995106518903      20428.07288     20469.0109
---
> 130091.0      260.182 256.10355987055016      98.0    0.0     142.9268095075238       143.06995106518906      20428.07288     20469.0109
{noformat}

I think this is just something about decimal precision, not a correctness issue.

> Enable all q-tests for multi-insertion [Spark Branch]
> -----------------------------------------------------
>
>                 Key: HIVE-8533
>                 URL: https://issues.apache.org/jira/browse/HIVE-8533
>             Project: Hive
>          Issue Type: Test
>          Components: Spark
>            Reporter: Chao
>            Assignee: Chao
>         Attachments: HIVE-8533.1-spark.patch
>
>
> As HIVE-8436 is done, we should be able to enable all multi-insertion related tests. This JIRA is created to track this and record any potential issue encountered. 



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