lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <>
Subject RE: ReadOnlyMultiSegmentReader bitset id vs doc id
Date Tue, 28 Apr 2009 20:42:13 GMT
What is the problem exactly? Maybe you use the new Collector API, where the
search is done for each segment, so caching does not work correctly?


Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen


From: patrick o'leary [] 
Sent: Tuesday, April 28, 2009 10:31 PM
Subject: ReadOnlyMultiSegmentReader bitset id vs doc id



I've got a filter that's storing document id's with a geo distance for
spatial lucene using a bitset position for doc id,
However with a MultiSegmentReader that's no longer going to working.

What's the most appropriate way to go from bitset position to doc id now?


View raw message