ASF GitHub Bot logged work on HIVE-22239:

                Author: ASF GitHub Bot
            Created on: 11/Oct/19 09:00
            Start Date: 11/Oct/19 09:00
    Worklog Time Spent: 10m 
      Work Description: kgyrtkirk commented on pull request #787: HIVE-22239
URL: https://github.com/apache/hive/pull/787#discussion_r333889584

 File path: 
 @@ -1946,6 +2022,8 @@ public Object process(Node nd, Stack<Node> stack, 
NodeProcessorCtx procCtx,
             pred = jop.getConf().getResidualFilterExprs().get(0);
           // evaluate filter expression and update statistics
+          final boolean uniformWithinRange = HiveConf.getBoolVar(
 Review comment:
   unused varibale (remove before committing)
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 326799)
    Time Spent: 4h 40m  (was: 4.5h)

> Scale data size using column value ranges
> -----------------------------------------
>                 Key: HIVE-22239
>                 URL: https://issues.apache.org/jira/browse/HIVE-22239
>             Project: Hive
>          Issue Type: Improvement
>          Components: Physical Optimizer
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-22239.01.patch, HIVE-22239.02.patch, 
> HIVE-22239.03.patch, HIVE-22239.04.patch, HIVE-22239.04.patch, 
> HIVE-22239.05.patch, HIVE-22239.05.patch, HIVE-22239.patch
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
> Currently, min/max values for columns are only used to determine whether a 
> certain range filter falls out of range and thus filters all rows or none at 
> all. If it does not, we just use a heuristic that the condition will filter 
> 1/3 of the input rows. Instead of using that heuristic, we can use another 
> one that assumes that data will be uniformly distributed across that range, 
> and calculate the selectivity for the condition accordingly.

This message was sent by Atlassian Jira

Reply via email to