: I override the seek() and next() methods of FilterTermDocs.
: The problem is the although my seek() method is being called,
: my next() method is not. Thus I never get to iterate through
: my list, and only receive results corrasponding to its first
: element.
It's pretty much impossible to gu
I already have this implemented with a filter. Its working alright, but
sends my running time
from .1 sec to .4 sec - thats no big deal now but we hope to eventually grow
the archive to
an insanely large size. Besides, I think the FilterIndexReader is a
powerfull tool, and I'd
like to get it worki
Wouldn't it be easier to just make a Filter? That's what they were
intended for.
Especially, if by "certain set", you mean that these are pre-defined
values, you could create your filters at start-up time and use
CachingWrapperFilter to keep them around.
Either way, I suspect it would be much si
I am trying to use a Filter Index Reader to
provide access only to the subset of my archive
for which a certain field contains one of a given
list of values.
The idea is to create a special term for this field
that means 'any term in the list', and add an 'AND'
clause to every query, to enforce t
