[
https://issues.apache.org/jira/browse/LUCENE-7066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182777#comment-15182777
]
ASF subversion and git services commented on LUCENE-7066:
---------------------------------------------------------
Commit 8c36347928efd20977acc120690ab5f8d5ccd4b7 in lucene-solr's branch
refs/heads/branch_6_0 from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8c36347 ]
LUCENE-7066: Optimize PointRangeQuery for the case that all documents have a
value and all points from the segment match.
> 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: [email protected]
For additional commands, e-mail: [email protected]
