> >>> MultiSearcher has a few aspects I don't like. > >> > >> Do you mean the score differences vs IndexSearcher(MultiReader), or > >> is there something else? > > And rewrite does not work properly. And to get 30 docs over 3 > > indexes, you ask for 90. And sort twice. > > I'm thinking we stick with MultiReader, but improve it so that when > sorting by fields can use a [new FieldCache like] API such that gives > it the benefits that MultiSearcher has. Ie, best of both worlds.
That would be very nice! In my code, I generally have an index organization layer using Readers and combining them to MultiReaders. The Search API is mostly decoupled from that, so when I do a search, I instantiate a IndexSearcher using any "abstract" Reader without knowing if it is a MultiReader, Directory/SegmentReader or whatever. If you are working with this code design, your suggestion is very important! Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
