[
https://issues.apache.org/jira/browse/SOLR-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906857#comment-13906857
]
Manuel Lenormand commented on SOLR-1223:
----------------------------------------
For simplification let's assume we have all the clauses cached as
filterQueries, namely bitsSets. Let's say they were warmed in a new-searcher.
All we need now is creating a new bitSet merged out of the logical OR/AND
between the cached queryFilters.
Looking at QueryComponent.prepare (line 167) we add a new queryParsed filter to
the responseBuilder, so before this stage we need to retrieve the cachedFilters
(from SolrIndexSearcher) and put a new cachedFilter out of the merged bitSet.
> Query Filter fq with OR operator
> --------------------------------
>
> Key: SOLR-1223
> URL: https://issues.apache.org/jira/browse/SOLR-1223
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Brian Pearson
>
> See this
> [issue|http://lucene.472066.n3.nabble.com/Query-Filter-fq-with-OR-operator-td499172.html]
> for some background. Today, all of the Query filters specified with the fq
> parameter are AND'd together.
> This issue is about allowing a set of filters to be OR'd together (in
> addition to having another set of filters that are AND'd). The OR'd filters
> would of course be applied before any scoring is done.
> The advantage of this feature is that you will be able to break up complex
> filters into simple, more cacheable filters, which should improve
> performance.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
