[
https://issues.apache.org/jira/browse/LUCENE-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926140#comment-13926140
]
Uwe Schindler commented on LUCENE-5495:
---------------------------------------
By the way: One trick to maybe improve speed if you want chanined AND-Filters.
There is no need to use BooleanFilter here, just chain FilteredQuery. This will
automatically (depending on filterstrategy) do exactly what you want:
- use {{new FilteredQuery(new FilteredQuery(query, filter1), filter2)}}
- set a filter strategy according to your needs. If bits() has *faaaaaast*
random access, use the default one. In that case, the resulting bits() instance
of {{filter1}} will passed as {{acceptDocs}} to {{filter2.getDocIdSet()}} and
the result of this will be passed as {{acceptDocs}} to query's {{scorer()}}.
But all this depends on your caching needs and performance of your random
access impls.
> Boolean Filter does not handle FilterClauses with only bits() implemented
> -------------------------------------------------------------------------
>
> Key: LUCENE-5495
> URL: https://issues.apache.org/jira/browse/LUCENE-5495
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: 4.6.1
> Reporter: John Wang
> Attachments: LUCENE-5495.patch, LUCENE-5495.patch
>
>
> Some Filter implementations produce DocIdSets without the iterator()
> implementation, such as o.a.l.facet.range.Range.getFilter().
> Currently, such filters cannot be added to a BooleanFilter because
> BooleanFilter expects all FilterClauses with Filters that have iterator()
> implemented.
> This patch improves the behavior by taking Filters with bits() implemented
> and treat them separately.
> This behavior would be faster in the case for Filters with a forward index as
> the underlying data structure, where there would be no need to scan the index
> to build an iterator.
> See attached unit test, which fails without this patch.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
