[
https://issues.apache.org/jira/browse/LUCENE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237417#comment-16237417
]
Adrien Grand edited comment on LUCENE-8017 at 11/3/17 10:39 AM:
----------------------------------------------------------------
Sure, but creating a collection when you have an array is just a matter of
wrapping it with Arrays.asList (O(1) memory), while if you have a collection
and need an array, you need to materialize the array (O( n) memory)?
was (Author: jpountz):
Sure, but creating a collection when you have an array is just a matter of
wrapping it with Arrays.asList (O(1) memory), while if you have a collection
and need an array, you need to materialize the array (O(n) memory)?
> FunctionRangeQuery and FunctionMatchQuery can pollute the QueryCache
> --------------------------------------------------------------------
>
> Key: LUCENE-8017
> URL: https://issues.apache.org/jira/browse/LUCENE-8017
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Attachments: LUCENE-8017.patch, LUCENE-8017.patch, LUCENE-8017.patch
>
>
> The QueryCache assumes that queries will return the same set of documents
> when run over the same segment, independent of all other segments held by the
> parent IndexSearcher. However, both FunctionRangeQuery and
> FunctionMatchQuery can select hits based on score, which depend on term
> statistics over the whole index, and could therefore theoretically return
> different result sets on a given segment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
