Hello guys,
I need additions and deletions of documents to the index to be ATOMIC
(they either happen to completion or not at all).
On top of this, I need updates (which I currently implement with a
deletion of the document followed by an addition) to be ATOMIC and
DURABLE (once I return from
Hello,
I am trying to use transactions with the Lucene + BDB package. I want
to be able to open a directory, and IndexWriter and then do things
like:
open IndexWriter
start transaction 1
write something to the index
commit transaction 1 (or abort it)
start transaction 2
write something else to
Hi Luceners!
I am trying to use transcations in the Berkeley DB + Lucene package
from the sandbox. Has anyone done this succesfully? I dont see any
transactions being commited or aborted in the code, so I wonder if
transactions actually work (shouldnt the main transaction that is used
for opening
of the issues.
good luck,
andy g
On Mon, 20 Sep 2004 19:36:51 -0300, Christian Rodriguez
[EMAIL PROTECTED] wrote:
Hi everyone,
I am trying to use the Lucene + BDB integration from the sandbox
(http://cvs.apache.org/viewcvs.cgi/jakarta-lucene-sandbox/contributions/db/).
I
Hi everyone,
I am trying to use the Lucene + BDB integration from the sandbox
(http://cvs.apache.org/viewcvs.cgi/jakarta-lucene-sandbox/contributions/db/).
I installed C Berkeley DB 4.2.52 and I have the Lucene jar file.
I have an example program that indexes 4 small text files in a
directory
