At some point I made some issue like "make all SolrCloud communication via javabin by default".
That made it so that CloudSolrClient started talking javabin by default, as well as our internal usage of other clients (where we turned it on). This issue did not include changing the defaults for the non cloud clients. If someone thought that was a good idea, the upcoming 6 release would be a good time to make the change. - Mark On Thu, Nov 5, 2015 at 6:30 AM Alessandro Benedetti <[email protected]> wrote: > Hi guys, > I was taking a look to the implementation details to understand how Solr > requests are written by SolrJ APIs. > The interesting classes are : > > *org.apache.solr.client.solrj.request.RequestWriter* > > *org.apache.solr.client.solrj.impl.BinaryRequestWriter* ( wrong package ? > ) > > I discovered that : > > *CloudSolrClient *- is using the javabin format ( *BinaryRequestWriter*) > *HttpSolrClient *and* LBHttpSolrClient* - are using the *RequestWriter* ( > which writes xml) > > In consequence the ConcurrentUpdateSolrClient is using the xml > ResponseWriter as well. > > Is there any reason in this ? > I did know that the javabin format is the most efficient for Solr > requests. > Why the xml RequestWriter is still used as default with those SolrClients ? > > Cheers > > > -- > -------------------------- > > Benedetti Alessandro > Visiting card : http://about.me/alessandro_benedetti > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England > -- - Mark about.me/markrmiller
