hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-22238) PK/FK selectivity estimation underscales estimations
Date Fri, 08 Nov 2019 08:03:00 GMT


Hive QA commented on HIVE-22238:

Here are the results of testing the latest attachment:

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

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
was found in seen patch url's cache and a test was probably run already on it. Aborting...

This message is automatically generated.

ATTACHMENT ID: 12985234 - PreCommit-HIVE-Build

> PK/FK selectivity estimation underscales estimations
> ----------------------------------------------------
>                 Key: HIVE-22238
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Statistics
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-22238.01.patch, HIVE-22238.02.patch, HIVE-22238.03.patch, HIVE-22238.04.patch,
HIVE-22238.05.patch, HIVE-22238.05.patch, HIVE-22238.05.patch, HIVE-22238.05.patch, HIVE-22238.05.patch,
HIVE-22238.06.patch, HIVE-22238.06.patch, HIVE-22238.07.patch, HIVE-22238.09.patch, HIVE-22238.10.patch,
HIVE-22238.10.patch, HIVE-22238.10.patch, HIVE-22238.10.patch
>          Time Spent: 40m
>  Remaining Estimate: 0h
> at [this point|]
the parent operators rownum is scaled according to pkfkselectivity
> however [pkfkselectivity is computed|]
on a whole subtree.
> Scaling it by that amount will count in estimation already used when parentstats was depending on the number of upstream joins - this may lead to severe underestimations
> what happened was:
> * optimization was able to push the filter to the other side of the join
> * as a result the incoming data was already filtered
> * scaling down by the PK selectiviy - was actually already there...but a new "scaling"

This message was sent by Atlassian Jira

View raw message