You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2016/03/04 17:04:40 UTC

[jira] [Updated] (LUCENE-7066) Optimize the "everything matches" case for point range queries

     [ https://issues.apache.org/jira/browse/LUCENE-7066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrien Grand updated LUCENE-7066:
---------------------------------
    Attachment: LUCENE-7066.patch

Here is a patch.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org