hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20039) Bucket pruning: Left Outer Join on bucketed table gives wrong result
Date Wed, 04 Jul 2018 23:12:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-20039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533097#comment-16533097
] 

Hive QA commented on HIVE-20039:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12930204/HIVE-20039.01-branch-3.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/12384/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12384/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12384/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12930204/HIVE-20039.01-branch-3.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: 12930204 - PreCommit-HIVE-Build

> Bucket  pruning: Left Outer Join on bucketed table gives wrong result
> ---------------------------------------------------------------------
>
>                 Key: HIVE-20039
>                 URL: https://issues.apache.org/jira/browse/HIVE-20039
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.3.2
>            Reporter: Deepak Jaiswal
>            Assignee: Deepak Jaiswal
>            Priority: Major
>             Fix For: 4.0.0, 3.2.0
>
>         Attachments: HIVE-20039.01-branch-3.patch, HIVE-20039.1.patch, HIVE-20039.2.patch,
HIVE-20039.3.patch, HIVE-20039.4.patch
>
>
> Left outer join on bucketed table on certain cases gives wrong results.
> Depending on the order in which the table-scans are walked through, the FilterPruner
might end up using the wrong table scan's table properties on the other table.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message