[
https://issues.apache.org/jira/browse/LUCENE-7066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181822#comment-15181822
]
Nicholas Knize edited comment on LUCENE-7066 at 3/5/16 7:27 PM:
----------------------------------------------------------------
[~jpountz] I think this is an important optimization for any numeric index with
low variance - which is more common than not. The patch LGTM, and since
PointValues are a big feature for this release I'd rather see the improvement
make it now than wait.
was (Author: nknize):
[~jpountz] I think this is an important optimization for any numeric index with
high variance - which is more common than not. The patch LGTM, and since
PointValues are a big feature for this release I'd rather see the improvement
make it now than wait.
> Optimize the "everything matches" case for point range queries
> --------------------------------------------------------------
>
> Key: LUCENE-7066
> URL: https://issues.apache.org/jira/browse/LUCENE-7066
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-7066.patch
>
>
> Now that points have a getDocCount statistic, we could optimize execution of
> range queries in the case that the range's lower bound is less that the
> field's min value and the range's upper bound is greater than the field's max
> value.
> I would expect such an optimization to kick in frequently for users who store
> time series in their indices as it is quite frequent for ranges to cover
> entire segments or even entire indices.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
