[ https://issues.apache.org/jira/browse/HIVE-17040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605030#comment-16605030 ]
Hive QA commented on HIVE-17040: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12938538/HIVE-17040.04.patch {color:red}ERROR:{color} -1 due to build exiting with an error Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/13611/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13611/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13611/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12938538/HIVE-17040.04.patch was found in seen patch url's cache and a test was probably run already on it. Aborting... {noformat} This message is automatically generated. ATTACHMENT ID: 12938538 - PreCommit-HIVE-Build > Join elimination in the presence of FK relationship > --------------------------------------------------- > > Key: HIVE-17040 > URL: https://issues.apache.org/jira/browse/HIVE-17040 > 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.04.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 (v7.6.3#76005)