hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-13096) Cost to choose side table in MapJoin conversion based on cumulative cardinality
Date Mon, 22 Feb 2016 04:40:18 GMT


Hive QA commented on HIVE-13096:

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 4 failed/errored test(s), 9800 tests executed
*Failed tests:*
TestSparkCliDriver-timestamp_lazy.q-bucketsortoptimize_insert_4.q-date_udf.q-and-12-more -
did not produce a TEST-*.xml file

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: 4 tests failed

This message is automatically generated.

ATTACHMENT ID: 12788905 - PreCommit-HIVE-TRUNK-Build

> Cost to choose side table in MapJoin conversion based on cumulative cardinality
> -------------------------------------------------------------------------------
>                 Key: HIVE-13096
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Physical Optimizer
>    Affects Versions: 2.0.0, 2.1.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-13096.01.patch, HIVE-13096.patch
> HIVE-11954 changed the logic to choose the side table in the MapJoin conversion algorithm.
Initial heuristic for the cost was based on number of heavyweight operators.
> This extends that work so the heuristic is based on accumulate cardinality. In the future,
we should choose the side based on total latency for the input.

This message was sent by Atlassian JIRA

View raw message