Hi,
I am trying to use a shared IndexWriter instance for a multi-thread
application. Surprisingly, this under performs by creating a writer
instance within a thread.
My code is as follow. Can someone help explain why? Thanks.
Scenario 1: shared IndexWriter instance
RAMDirectory ramDir = new RA
Just reading Apache Solr Enterprise Search Server and was interested in
pages 152, 153 dismax and DisjunctionMaxQuery and automatic Phrase
Boosting. I would like to incorporate this into a standard Lucene setup,
non solr, whats the best way to do that.
In fact I'm already doing something very
Something that did change at some point, can't remember when, was the
way that discarded but not explicitly closed searchers/readers are
handled. I think that they used to get garbage collected, causing
open files to be closed, but now need to be explicitly closed. Sounds
to me like you are openi
Can you show the code? In particular are you re-opening
the index writer?
Bottom line: This isn't a problem anyone expects
in 3.1 absent some programming error on your
part, so it's hard to know what to say without
more information.
3.1 has other problems if you use spellcheck.collate,
you might
Thanks for the reply. I'm still having trouble. I've made some changes to
use commit over close, but I'm not seeing much in terms of changes on what
seems like ever increasing open file handles. I'm developing on Mac OS X
10.6 and testing on Linux CentOS 4.5. My biggest problem is I can't tell
