21:01
To: java-user@lucene.apache.org
Subject: Re: IndexWriter: setRAMBufferSizeMB
It's complicated.
In 2.3, you can use IW.flush to write docs to disk. But that method
will be deprecated in 2.4 and replaced with commit. Or, you
can close.
If application (jvm) dies or killed, the index w
e.apache.org
> Subject: Re: IndexWriter: setRAMBufferSizeMB
>
>
> It's complicated.
>
> In 2.3, you can use IW.flush to write docs to disk. But that method
> will be deprecated in 2.4 and replaced with commit. Or, you
> can close.
>
> If application (jvm) dies
pache.org
Subject: Re: IndexWriter: setRAMBufferSizeMB
Well ... every time the RAM buffer is full, a new segment is flushed
to the Directory, but that is not necessarily a "commit" in that
an IndexReader would see the new segment, nor, that the segment would
survive if the machine suddenly
9:34
> To: java-user@lucene.apache.org
> Subject: Re: IndexWriter: setRAMBufferSizeMB
>
> Well ... every time the RAM buffer is full, a new segment is flushed
> to the Directory, but that is not necessarily a "commit" in that
> an IndexReader would see the new segment, nor
Well ... every time the RAM buffer is full, a new segment is flushed
to the Directory, but that is not necessarily a "commit" in that
an IndexReader would see the new segment, nor, that the segment would
survive if the machine suddenly crashed.
You should't rely on when specifically IndexWriter m
Hi,
if I understand this property correctly every time the ram buffer is full it
gets automaticaly written to disk. Something like a commit in a database.
Thus if my application dies, all docs in the buffer get lost. Right?
If so, is there any event/callback etc. which informs my application that
