: But, can you then explain why Apache Nutch with SolrJ had this problem? : It seems that by default SolrJ does use XML as transport format. We have : always used SolrJ which i assumed would default to javabin, but we had : this exact problem anyway, and solved it by stripping non-character code : points. : : When we use SolrJ for querying we clearly see wt=javabin in the logs, : but updates showed the problem. Can we fix it anywhere?
wt=javabin indicates what *response* format the client (ie: solrj) is requesting from the server ... the format used for the *request* body is determined by the client based on the Content-Type of the ContentStream it sends to Solr. When using SolrJ, and sending an arbitrary/abstract SolrRequest objects, the "RequestWriter" configured on the SolrClient is what specifies the Content-Type to use (and is in charge of serializing the java objects appropriately) BinaryRequestWriter (which uses javabin format to serialize SolrRequest objects when building ContentStreams) has been the default since Solr 5.5/6.0 (see SOLR-8595) -Hoss http://www.lucidworks.com/
