I'm confused by what you mean - there is no difference between something being
marked as deleted and deleted. (Since it's not removed from the index until
optimization)
I've found that unless I close(), the document isn't even marked for deletion.
And if I recall, I think I also had to close
Hi, I just wanted to check the wording on this FAQ entry to see if it means
what it says, or what I'd prefer it to mean. The entry is:
"Is the IndexSearcher thread-safe?
Yes, IndexSearcher is thread-safe. Multiple search threads may access the index
concurrently without any problems. "
So, the
I know there's a little bit of trickery when it comes to deletes (i.e. it's
still in the index until optimize, still available to open readers, etc)
however I'm having this problem:
I've implemented a call to delete by term. It tells me that it deleted 1 item,
but then I go and open a new read
And together we will rule the galaxy as father and son?
-Original Message-
From: Rob Young [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 2:22 PM
To: java-user@lucene.apache.org
Subject: Join Me
-
To uns
I have a set of indexes containing business information (name, address, phone,
etc). There are a couple particular companies that don't come up when people
search for them. I've used our debugging app that allows lucene queries to be
executed directly, and I have confirmed this.
I can find t
I didn't notice any exceptions and unfortunately I built these 2 long enough
ago that I have no logs left.
Anyway, I built 2 indexes using a process that I've built hundreds of indexes
successfully with, and these two indexes seem to contain no documents despite
being pretty large (about a gig)
Hello, all.
I'm trying to optimize an index, and I get this exception... A copy of this
index made a couple weeks ago optimized correctly, and I don't THINK there have
been any changes made to this index since there. (but there may have been)
I also couldn't find anything about this in the
