Yonik Seeley wrote:
On 1/16/07, robert engels <[EMAIL PROTECTED]> wrote:
You have the same problem if there is an existing reader open, so
what is the difference? You can't remove the segments there either.
The disk space for the segments is currently removed if no one has
them open... this is quite a bit different than guaranteeing that a
reader in the future will be able to open an index in the past.
Also remember the original issue here is that NFS (and perhaps other
filesystems where people would naturally expect Lucene to "just work")
doesn't provide this "protection" of not deleting files that are open
for reading.
This was the starting point that led to the idea of "explicit
commits".
If writer and reader can agree that certain segments_N are "valuable"
(commits) and others are just the automatic checkpoints that Lucene
needs to do (flushing, merging) then by agreeing on how deletes will
happen to the "valuable" segments_N files, readers can refresh
accordingly and never have their segments deleted out from under
them.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
