: You are correct on that point, but it seems rather difficult for you : to do the range caching and have it work across any document updates : (unless a lot more notification interfaces are added to Lucene), so I : guess I don't see the point of your caching.
i haven't read the patch, but based on the jira description i don't think this is attempting to reuse cached info across updates -- i think it's just trying to address the issue of eliminating redundent TermEnum/TermDoc iterating for similar ranges. : Given, a sample date range: : 01/01/2001 to 01/01/2007 : has a bit set associated. : : If I did a query for : 12/31/2000 to 01/01/2007 : : the current filter code would cause a new filter to be created (which : is what I assume you are attempting to solve). Under you solution I i don't think it's an attempt at reducing the number of bitsets, just at reducing the amount of time spent computing those bitsets -- with the filter on "01/01/2001 to 01/01/2007" already in the cache, the filter on "12/31/2000 to 01/01/2007" only needs to look at the terms between 12/31/2000 and 01/01/2001 - and can and the result with the existing bitset. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
