David Johnson wrote:
Digging into the internals of Jackrabbit, we have noticed that there is an implementation of RangeQuery that essentially walks the results if the # of query terms is greater than what Lucene can handle. Reading the Lucene documentation, it looks like Filters are the recommended method of implementing "large" range queries, and also seem like a natural for matching node types - i.e., select * from Column
As we are expecting to reach a count of 1.000.000+ nodes in one of our repositories I'm always interested in any performance improvements. Is anyone investigating in this proposal? Or could at least anyone tell me if it's worth investigating? ;)
Cheers, Christoph
