: times. Is there any way to have the index keep its caches when the only thing : that happens is deletions, then invalidate them when it's time to actually add : data? It would have to be something I can dynamically change when switching : between deletions and the daily import.
The problem is a delete is a genuine hange that invalidates hte cache objects. The worst case is the QueryResultCache where a deleted doc would require shifting all of hte other docs up in any result set that it matched on -- even if that doc isn't in the actual DocSlice that's cached (ie: the cached version of results 50-100 is affected by deleting a doc from 1-50) In theory something like the filterCache could be warmed by copying entires from the old cache and just unsetting the bits corrisponding to the deleted docs -- except that i'm pretty sure even if all you do is delete some docs, a MergePolicy *could* decide to merge segments and collapse away the docids of the delete docs. -Hoss
