Ning Li wrote:
It's only upon successfully writing the new segments that Lucene will
write a new "segments" file referring to the new segments. After
that, it removes the old segments. Since it makes these changes in
the correct order, it should be the case that disk full exception
never affects the already written index.
Lucene could produce an inconsistent index if addIndexes(Directory[])
does not run to its completion. The following is my recent comment on
another issue.
"This makes me notice a bug in current addIndexes(Directory[]). In
current addIndexes(Directory[]), segment infos in S are added to T's
"segmentInfos" upfront. Then segments in S are merged to T several at
a time. Every merge is committed with T's "segmentInfos". So if a
reader is opened on T while addIndexes(Directory[]) is going on, it
could see an inconsistent index."
Oh, ugh. I will open an issue for this. I think we should try to fix this.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
