Many thanks for your reply.
We're running Solr 4.4.0 in production, but SolrJ 3.6 is still used by our CMS connector. I will place your reply as a comment in our own Jira and do the necessary changes later when we are ready to upgrade SolrJ for our connector.
Erlend On 10/4/13 4:05 PM, Shawn Heisey wrote:
On 10/4/2013 7:16 AM, Erlend Garåsen wrote:[2013-10-03 17:37:56.981] WARNING Using deprecated class: XmlUpdateRequestHandler -- replace with UpdateRequestHandler [2013-10-03 17:37:56.983] WARNING Using deprecated class: BinaryUpdateRequestHandler -- replace with UpdateRequestHandler How do I actually configure UpdateRequestHandler as a substitute for these two handlers? Now I'm getting the following error when I'm starting Solr: [2013-10-04 14:47:30.794] SEVERE org.apache.solr.common.SolrException: Unsupported ContentType: application/octet-stream Not in: [application/xml, text/csv, text/json, application/csv, application/javabin, text/xml, application/json] ... Here's my new configuration for the old BinaryUpdateRequestHandler which does not work: <requestHandler name="/update/javabin" class="solr.UpdateRequestHandler" > <lst name="defaults"> <str name="df">content_no</str> </lst> </requestHandler>They are *warnings*, not errors. The indirectly (but not clearly) stated message is "this class will no longer work in Solr 5.0, but you can continue to use it in all Solr 4.x versions." What you'll need to do to eliminate the messages: 1) Configure the /update handler to use solr.updateRequestHandler. See the example config for the latest 4.x version. 2) Stop using /update/javabin (or its cousins, like /update/json) in clients. Unless you are explicitly setting this path, normally this only happens if you're using SolrJ 3.6.2 or earlier and BinaryRequestWriter. If you're using SolrJ 4.0 or later, it will only use /update. 3) Get rid of all update handlers in your config except /update. This handler will accept all valid request formats, but it requires a correct Content-Type HTTP header, which SolrJ 4.x will provide. One of your error messages indicates the values that it will accept. Remember what I started with: You do not *NEED* to do this until you're ready to upgrade to Solr 5.0, which is not going to be available anytime soon. As of this writing, version 4.5.0 is being copied to mirrors and can be downloaded from some of them. The announcement of its release is due in the next day or two. If the mirror copy goes slow enough, it may take three days. Thanks, Shawn
