lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Miller <markrmil...@gmail.com>
Subject Re: ReadOnlyMultiSegmentReader bitset id vs doc id
Date Tue, 28 Apr 2009 21:12:11 GMT
You might check out this Solr exchange : 
http://www.lucidimagination.com/search/document/b2ccc68ca834129/lucene_2_9_migration_issues_multireader_vs_indexreader_document_ids

There are a few suggestions throughout.


-- 
- Mark

http://www.lucidimagination.com



Uwe Schindler wrote:
>
> 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
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
> ------------------------------------------------------------------------
>
> *From:* patrick o'leary [mailto:pjaol@pjaol.com]
> *Sent:* Tuesday, April 28, 2009 10:31 PM
> *To:* java-dev@lucene.apache.org
> *Subject:* ReadOnlyMultiSegmentReader bitset id vs doc id
>
>  
>
> hey
>
> 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?
>
> Thanks
> Patrick
>





---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message