I also have trouble understanding why you would care how solrj talks
to the server... the javabin option is the fastest available.
If you need to give JSON to a client, can't you just put in a proxy?
On Sep 15, 2008, at 12:46 AM, Erik Hatcher wrote:
If the client wants JSON, then it seems passing it straight from
Solr through the application server tier (hypothetical architecture
here) to the client as JSON is a nice way to go. If the client can
talk directly to Solr, then definitely just &wt=json and carry on,
but more often then not an application server is in the middle.
Curious: SolrJ with javabin format to an app server that converts to
JSON, pros/cons to the raw response writer?
What are others doing in the Ajaxed client world with Solr?
Erik
On Sep 15, 2008, at 12:01 AM, Jon Baer wrote:
Hmm am I missing something but isn't the real point of SolrJ to be
able to use the binary (javabin) format to keep it small / tight /
compressed? I have had to proxy Solr recently and found just
throwing a SolrDocumentList as a JSONArray (via json.org libs)
works pretty well (YMMV). I was just under the impression that the
Java to Java bridge was the best way to go ...
It would be nice to have util methods on the SolrDocumentList
(toJSON(), toXML(), etc) maybe?
- Jon
On Sep 14, 2008, at 11:14 PM, Erik Hatcher wrote:
On Sep 14, 2008, at 2:51 PM, Julio Castillo wrote:
What is the status of JSON support via SolrJ?
Requires a custom ResponseParser. See SOLR-402 for a couple of
implementation ideas:
<https://issues.apache.org/jira/browse/SOLR-402>
Maybe this code is no longer current to trunk?
I want to be able to specify a parser such as the
XMLResponseParser on my
SolrServer. What are my options?
Use SolrServer#setParser() for one of the above implementations.
I guess I could get an XML response and then convert it to JSON?
I rather
not.
Ewww, don't do that.
There is a JIRA entry SOLR-402, but real resolution to it per the
comments
that follow in the feature request.
https://issues.apache.org/jira/browse/SOLR-402
Did the RawResponseParser work for you? If so, we can build that
into Solr trunk - +1. I shoulda done that a while ago, sorry.
This actually fits well with SOLR-620, in my nefarious plans to
build a web framework out of Solr ;)
Erik
