[LUCENE-3212] Supply FilterIndexReader based on any o.a.l.search.Filter

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 4.0-ALPHA
• Fix Version/s: 4.0-ALPHA
• Component/s: core/index, core/search
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 18/Jun/11 11:25
• Updated: 22/Nov/24 09:50
• Resolved: 30/Oct/11 15:36

Description

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.

Issue Links

• is related to: LUCENE-1536 if a filter can support random access API, we should use it