hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-15683) Measure performance impact on group by by HIVE-15580
Date Wed, 08 Feb 2017 08:21:41 GMT


Hive QA commented on HIVE-15683:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 47 failed/errored test(s), 9595 tests executed
*Failed tests:*
TestDerbyConnector - did not produce a TEST-*.xml file (likely timed out) (batchId=235)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[index_auto_mult_tables_compact] (batchId=33)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query23] (batchId=223)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 47 tests failed

This message is automatically generated.

ATTACHMENT ID: 12851553 - PreCommit-HIVE-Build

> Measure performance impact on group by by HIVE-15580
> ----------------------------------------------------
>                 Key: HIVE-15683
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Spark
>    Affects Versions: 2.2.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>         Attachments: HIVE-15683.patch
> HIVE-15580 changed the way the data is shuffled for order by: instead of using Spark's
groupByKey to shuffle data, Hive on Spark now uses repartitionAndSortWithinPartitions(), which
generates (key, value) pairs instead of original (key, value iterator). This might have some
performance implications, but it's needed to get rid of unbound memory usage by {{groupByKey}}.
> Here we'd like to compare group by performance with or w/o HIVE-15580. If the impact
is significant, we can provide a configuration that allows user to switch back to the original
way of shuffling.
> This work should be ideally done after HIVE-15682 as the optimization there should help
the performance here as well. 

This message was sent by Atlassian JIRA

View raw message