"Maybe you aren't using the IndexReader instance returned by reopen(), but instead are continuing to use the instance on which you called reopen()? It's tough to figure this kind of thing out without looking at the code."
That was it, I was not using the newly (re)opened index. By the way, one last question. It doesn't matter for this because I'm indexing one huge document at a time, and then committing. But later, I will also be indexing very small documents frequently. In that case, it would seem that if I index a very small document, I don't want to be thrashing with a commit after each one, and then a reopen of the reader and reconstruction of my searcher. Do others manage this type of thing with a thread that fires at intervals to commit if dirty? -- View this message in context: http://lucene.472066.n3.nabble.com/search-hits-not-returned-until-I-stop-and-restart-application-tp911711p912345.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
