hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-17040) Join elimination in the presence of FK relationship
Date Sun, 12 Aug 2018 19:39:00 GMT


Hive QA commented on HIVE-17040:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 10 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 14880 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestSparkCliDriver.testCliDriver[list_bucket_dml_2] (batchId=114)

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.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed

This message is automatically generated.

ATTACHMENT ID: 12935296 - PreCommit-HIVE-Build

> Join elimination in the presence of FK relationship
> ---------------------------------------------------
>                 Key: HIVE-17040
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Logical Optimizer
>    Affects Versions: 3.0.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Major
>         Attachments: HIVE-17040.01.patch, HIVE-17040.02.patch, HIVE-17040.patch
> If the PK/UK table is not filtered, we can safely remove the join.
> A simple example:
> {code:sql}
> SELECT c_current_cdemo_sk
> FROM customer, customer_address
> ON c_current_addr_sk = ca_address_sk;
> {code}
> As a Calcite rule, we could implement this rewriting by 1) matching a Project on top
of a Join operator, 2) checking that only columns from the FK are used in the Project, 3)
checking that the join condition matches the FK - PK/UK relationship, 4) pulling all the predicates
from the PK/UK side and checking that the input is not filtered, and 5) removing the join,
possibly adding a IS NOT NULL condition on the join column from the FK side.
> If the PK/UK table is filtered, we should still transform the Join into a SemiJoin operator.

This message was sent by Atlassian JIRA

View raw message