From what I understand you don't have to select a thing, the SolrCore
would detect SolrJ and do it automatically(?) ...
44. SOLR-486: Binary response format, faster and smaller
than XML and JSON response formats (use wt=javabin).
BinaryResponseParser for utilizing the binary format via SolrJ
and is now the default.
(Noble Paul, yonik)
On Sep 15, 2008, at 2:40 PM, Julio Castillo wrote:
Jon,
Is the binary (javabin) format implied by selecting the
RawResponseParser? I
guess I don't know what the javabin format is.
So you took a SolrDocumentList and converted it into a JSON Array?
Thanks
** julio
-----Original Message-----
From: Jon Baer [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 14, 2008 9:01 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrJ and JSON in Solr -1.3
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
