I don't have that use case. I start a transaction, open a directory,
create a reader or writer depending upon deletes or adds, perform
operations, close reader or writer, close directory, commit. It works
like a champ.
Aaron
-Original Message-
From: Oscar Picasso [mailto:[EMAIL PROTECT
If I remember correctly, with my code, I had to create and close the
IndexWriter inside a single transaction.
If the same IndexWriter is used for several transactions and there is a
rollback, it can corrupt the indexes.
It's just sligthly annoying but I am curious if you ran into this 'prob
I was aware of jacid. In its current form it could not be used with the
JCA connector because the DbDirectory opens the database. Given that I
was going to have to write some code, I decided to use Andi's code as a
starting point because it seemed cleaner and has seen wider use.
Regards,
Aaron
Hi,
Around one year ago, I made a Berkeley DB JE implementation of a Lucene
Directory. I was initially inspired by the Andi Vajda code.
I released it under an Apache License but didn't publicize it.
Lately I have read there is some talks about DB JE base directories so if
someone is in
Which class writes to the .frq?
I thought it's documentwriter, but the following code in the
documentwriter.java doesn't really do what fileformats says the .frq
file is like...
int postingFreq = posting.freq;
if (postingFreq == 1) // optimize
freq=1
