[
https://issues.apache.org/jira/browse/SOLR-10727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020123#comment-16020123
]
Mikhail Khludnev commented on SOLR-10727:
-----------------------------------------
+1
> Optimize faceting on empty docSet to return faster and not pollute filter
> cache
> -------------------------------------------------------------------------------
>
> Key: SOLR-10727
> URL: https://issues.apache.org/jira/browse/SOLR-10727
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: master (7.0)
>
> Attachments: SOLR_10727_SolrIndexSearcher_numDocs_0_docSet.patch
>
>
> In certain faceting circumstances (both classic SimpleFacets and JSON
> Facets), {{SolrIndexSearcher.numDocs(q,docSet)}} is invoked. numDocs can be
> improved to return early if the passed docSet (the base of documents to
> compute facets on) is empty. Since it doesn't today, it'll go create a
> filter cache entry (if it doesn't exist) for the query. Range faceting is a
> heavy user of this method since it'll be called for each range. If you're
> doing date range faceting and do time based sharding and have a time based
> filter query, then there's a decent chance the current index in question
> won't match the query. So lets not pollute the filter cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
