On 1/28/2014 8:01 AM, Alexandre Rafalovitch wrote: > What am I missing? Should I be looking at test classes: > https://github.com/apache/lucene-solr/tree/trunk/solr/solrj/src/test/org/apache/solr/client/solrj > ? They seem to be a little specialized to be reversing engineering > basic examples from. > > I am not trying to make a fuss, just understand what the baseline > situation is. And maybe get a couple of good pointers from people in > the know.
Something to get out of the way first is a discussion about EmbeddedSolrServer, which you mentioned. Every time it comes up, the people who've been committers for a really long time will mention that you shouldn't use the embedded server. Use a standalone server with the container programmed to only listen on localhost. I've never used the embedded server myself, and I'm told that the overhead from using HTTP on localhost is pretty small. I can't really use this as an excuse, but one of the problems with examples for SolrJ is that it is a very complex API, with several ways to do common tasks and lots of uncommon options/methods. When there are multiple ways to do something, it's usually because both ways have merit in different circumstances. What would you like to see in an example? I know a fair amount about SolrJ, and we have access to lots of smart people here, so how about we discuss what you think is missing? We can come up with something that will hopefully answer the top N questions a user might have. Side warning: SOLR-5604. Some of the workflow around various SolrServer implementations needs to change because HttpClient 4.3.x has deprecated a lot of methods used in SolrJ and custom code. Thanks, Shawn