Also, rollback is still possible after a commit as long as you're using
a deletion policy that keeps more than one commit around, by
opening the IndexWriter on a prior commit point.
Mike
Nadav Har'El wrote:
On Mon, Feb 23, 2009, Jason Rutherglen wrote about "Re:
IndexWriter.r
Nadav Har'El wrote:
On Mon, Feb 23, 2009, Jason Rutherglen wrote about "Re:
IndexWriter.rollback() logic":
Howdy An,
Commit means the changes are committed, there's no rollback at that
point.
Also in the futuer please post your questions to java-dev@lucene.apache.org
On Mon, Feb 23, 2009, Jason Rutherglen wrote about "Re: IndexWriter.rollback()
logic":
> Howdy An,
>
> Commit means the changes are committed, there's no rollback at that point.
>
> Also in the futuer please post your questions to java-dev@lucene.apache.org
Actua
: Also in the futuer please post your questions to java-dev@lucene.apache.org
I believe jason ment to type java-u...@lucene...
http://people.apache.org/~hossman/#java-dev
Please Use "java-u...@lucene" Not "java-...@lucene"
Your question is better suited for the java-u...@lucene mailing list ...
Howdy An,
Commit means the changes are committed, there's no rollback at that point.
Also in the futuer please post your questions to java-dev@lucene.apache.org
Take care,
Jason
On Mon, Feb 23, 2009 at 3:52 PM, An Hong wrote:
> A question about IndexWriter.rollback() logic. Its
A question about IndexWriter.rollback() logic. Its javadoc says that it "Close
the IndexWriter without committing any of the changes that have occurred since
it was opened." So if I do
1. Open IndexWriter
2. Add doc1
3. Commit (successfully)
4. Add doc2
5. PrepareCommit()
6.
