On 2/21/2013 10:00 AM, Jack Park wrote:
Interesting you should say that. Here is my solrj code:
public Solr3Client(String solrURL) throws Exception {
server = new HttpSolrServer(solrURL);
// server.setParser(new XMLResponseParser());
}
I cannot recall why I commented out the setParser line; something
about someone saying in another thread it's not important. I suppose I
should revisit my unit tests with that line uncommented. Or, did I
miss something?
The JSON results I painted earlier were from reading the document
online in the admin query panel.
Jack,
SolrJ defaults to the javabin response parser, which offers maximum
efficiency in the communication. Between version 1.4.1 and 3.1.0, the
javabin version changed and became incompatible with the old one.
The XML parser is a little bit less efficient than javabin, but is the
only way to get Solr/SolrJ to talk when one side is using a different
javabin version than the other side. If you are not mixing 1.x with
later versions, you do not need to worry about changing the response parser.
Thanks,
Shawn
