De-basing / re-basing docIDs, or how to effectively pass calculated values from a Scorer or Filter up to (Solr's) QueryComponent.process

In the code I'm working with, I generate a cache of calculated values as a by-product within a Filter.getDocidSet implementation (and within a Query-ized version of the filter and its Scorer method) . These values are keyed off the IndexReader's docID values, since that's all that's

Re: De-basing / re-basing docIDs, or how to effectively pass calculated values from a Scorer or Filter up to (Solr's) QueryComponent.process

Aaron, could you move this to solr-user? -Yonik http://www.lucidimagination.com On Tue, Oct 6, 2009 at 11:22 AM, Aaron McKee ucbmc...@gmail.com wrote: In the code I'm working with, I generate a cache of calculated values as a by-product within a Filter.getDocidSet implementation (and within

Re: De-basing / re-basing docIDs, or how to effectively pass calculated values from a Scorer or Filter up to (Solr's) QueryComponent.process

Might still be lucene-ish issue. We already have getSequentialSubReaders() on IR, in my patched version I augmented this with public readerIndex(), and getSubReaderStarts(). Pretty much impossible to do some postprocessing on gathered hits without at least one of these. On Tue, Oct 6, 2009 at