So what if documents are deleted in the meantime? Then the recursive merge
can't determine the X segments with the same size.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Clemens Marschner wrote:
So what if documents are deleted in the meantime? Then the recursive merge
can't determine the X segments with the same size.
If you read my previous message you'll find the answer:
Doug Cutting wrote:
It's actually a little more complicated than that, since (among
Hello all,
I used the delete(Term) method, then I looked at the index files, only one
file changed _1tx.del I found references to the file still in some of the
index files, so my question is how does Lucene handle deletes?
Thanks,
Rob
--
To unsubscribe, e-mail: mailto:[EMAIL
It just marks the record as deleted. The record isn't actually removed
until the index is optimized.
Scott
Rob Outar wrote:
Hello all,
I used the delete(Term) method, then I looked at the index files,
only one
file changed _1tx.del I found references to the file still in some
of the
This is via mergeFactor?
--- Doug Cutting [EMAIL PROTECTED] wrote:
The data is actually removed the next time its segment is merged.
Optimizing forces it to happen, but it will also eventually happen as
more documents are added to the index, without optimization.
Scott Ganyo wrote:
It
Merging happens constantly as documents are added. Each document is
initially added in its own segment, and pushed onto the segment stack.
Whenever there are mergeFactor segments on the top of the stack that are
the same size, these are merged together into a new single segment that
replaces
I see, so every mergeFactor documents they are compined into a single
new segment in the index, and only when optimize() is called do those
multiple segments get merged into a single segment.
In your example below that would mean that optimize() was called after
document 100 was added, hence a
No, in my example optimize() was never called. The merge rule operates
recursively. So, after 99 documents had been added the segment stack
contained nine indexes with ten documents and nine with one document.
When the hundredth document was added, the nine one document segments
were popped
