[
https://issues.apache.org/jira/browse/HIVE-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095915#comment-15095915
]
Lefty Leverenz commented on HIVE-11573:
---------------------------------------
[~asears] documented *hive.optimize.point.lookup* in the wiki so I'm removing
the TODOC2.0 label. (*hive.optimize.point.lookup.extract* does not need to be
documented because HIVE-11634 removed it.) Thanks, Andrew.
* [Configuration Properties -- hive.optimize.point.lookup.min |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.optimize.point.lookup.min]
> PointLookupOptimizer can be pessimistic at a low nDV
> ----------------------------------------------------
>
> Key: HIVE-11573
> URL: https://issues.apache.org/jira/browse/HIVE-11573
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Gopal V
> Assignee: Gopal V
> Fix For: 2.0.0
>
> Attachments: HIVE-11573.1.patch, HIVE-11573.2.patch,
> HIVE-11573.3.patch, HIVE-11573.4.patch, HIVE-11573.5.patch, HIVE-11573.6.patch
>
>
> The PointLookupOptimizer can turn off some of the optimizations due to its
> use of tuple IN() clauses.
> Limit the application of the optimizer for very low nDV cases and extract the
> sub-clause as a pre-condition during runtime, to trigger the simple column
> predicate index lookups.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
