hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-21857) Sort conditions in a filter predicate to accelerate query processing
Date Thu, 13 Jun 2019 14:26:00 GMT


Hive QA commented on HIVE-21857:

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: 12971632 - PreCommit-HIVE-Build

> Sort conditions in a filter predicate to accelerate query processing
> --------------------------------------------------------------------
>                 Key: HIVE-21857
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: CBO
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21857.01.patch, HIVE-21857.02.patch, HIVE-21857.03.patch
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Following approach similar to .
> To reorder predicates in AND conditions, we could rank each of elements in the clauses
in increasing order based on following formula:
> {code}
> rank = (selectivity - 1) / cost per tuple
> {code}
> Similarly, for OR conditions:
> {code}
> rank = (-selectivity) / cost per tuple
> {code}
> Selectivity can be computed with FilterSelectivityEstimator. For cost per tuple, we will
need to come up with some heuristic based on how expensive is the evaluation of the functions
contained in that predicate. Custom UDFs could be annotated.

This message was sent by Atlassian JIRA

View raw message