On 8/12/2011 4:18 PM, Shawn Heisey wrote:
On 8/12/2011 1:49 PM, Shawn Heisey wrote:
I am sure that I have more questions, but I may be able to answer a
lot of them myself if I can see better examples.
Thought of another question. My Perl build system uses DIH for all
indexing, but with the Java rewrite I am planning to do all actions
other than a full index rebuild using the /update handler. I have
autoCommit completely turned off in solrconfig.xml. Do I need to set
any parameters to ensure that nothing gets committed until I do a
server.commit() myself?
Thanks,
Shawn
Shawn, my experience with SolrJ in that configuration (no autoCommit) is
that you have control over commits: if you don't issue an explicit
commit, it won't happen. Re lifecycle: we don't use a static instance;
rather our app maintains a small pool of CommonsHttpSolrServer instances
that we re-use across requests. I think that will be preferable since I
don't think the underlying HttpClient is thread safe?
I haven't used CoreAdmin features, nor HTTP POST w/SolrJ, but I do see
an option to request that the server operate w/multipart post:
public CommonsHttpSolrServer(URL baseURL, HttpClient client,
ResponseParser parser, boolean useMultiPartPost)
-Mike
