[
https://issues.apache.org/jira/browse/LUCENE-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055116#comment-13055116
]
Uwe Schindler commented on LUCENE-3212:
---------------------------------------
It's similar, but I dont understand the impl there. I would simply override
getDeletedDocs to return the deleted docs ored with the filtered. Then you dont
need to override terms() and fields().
> Supply FilterIndexReader based on any o.a.l.search.Filter
> ---------------------------------------------------------
>
> Key: LUCENE-3212
> URL: https://issues.apache.org/jira/browse/LUCENE-3212
> Project: Lucene - Java
> Issue Type: Improvement
> Components: core/index, core/search
> Affects Versions: 4.0
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 4.0
>
>
> When coding LUCENE-2919 (PKIndexSplitter), Mike and me had the idea, how to
> effectively apply filters on the lowest level (before query execution). This
> is very useful for e.g. security Filters that simply hide some documents.
> Currently when you apply the filter after searching, lots of useless work was
> done like scoring filtered documents, iterating term positions (for
> Phrases),...
> This patch will provide a FilterIndexReader subclass (4.0 only, 3.x is too
> complicated to implement), that hides filtered documents by returning them in
> getDeletedDocs(). In contrast to LUCENE-2919, the filtering will work on
> per-segment (without SlowMultiReaderWrapper), so per segment search keeps
> available and reopening can be done very efficient, as the filter is only
> calculated on openeing new or changed segments.
> This filter should improve use-cases where the filter can be applied one time
> before all queries (like security filters) on (re-)opening the IndexReader.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
