There needs to be a way to create the aggregate docFreq table and keep it current under incremental changes to the indices on the various remote nodes.
I think you're getting ahead of yourself. Searchers are based on IndexReaders, and hence doFreqs don't change until a new Searcher is created. So long as this is true, and the central dispatch node uses a searcher, then a simple cache, perhaps that is pre-fetched, is all that's feasable. It shouldn't take that long to pre-fetch the cache when indexes are re-opened. Lets run before we sprint, and hey, let's even walk first by first fixing the bug in question.
Doug
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
