Hello, Sascha. That's right. You should close IndexWriter instance only when the applications itself is stopping. To make documents visible to newly created IndexReader instances commit() call is enough.
On May 4, 2014, at 2:46 AM, Sascha Janz <sascha.j...@gmx.net> wrote: > Hi, > > > > We use lucene 4.6, our application receives continuously new documents. > Mostly emails. We need the update near real time, so we open the IndexReader > with Directory.open and IndexWriter. > > > > Periodically we do a commit, e.g. every 200 documents. > > > > We used to close the IndexWriter on commit, and then open a new one. I read > in documentation this is quite expensive, tests also showed me this. So we > think about to only commit the IndexWriter and leave it open. So when should > we close the IndexWriter? I think about to leave it open and only close it, > when the server is shutting down. Is this a good idea? Any suggestions or > comments? Would be nice J > > > > Greetings > > Sascha > --- Denis Bazhenov <dot...@gmail.com> --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
