I think the high-level case is that if the index is shared, you want
the other readers to be able to see the updated deletes if they are
notified to reread the index (using something like reopen).
On Dec 11, 2006, at 2:59 PM, Yonik Seeley wrote:
On 12/11/06, Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
I believe (another colleague did work around this) the use case is
the desire to flush the deletes without having to close the reader
and reopen it, which is expensive because of FieldCache population.
Yes, but that doesn't answer *why* deletes must be flushed now as
opposed to later.
What's the higher level use-case behind needing to flush the deletes?
-Yonik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
