: I am not sure, didn't have a time to check all details... : Simply: old version of an application tried to send "<delete>" request, and : could not parse response due to (possible) schema changes and hardcoded
I just tested Solr 1.2 using the Solr 1.1 example solrconfig.xml and schema.xml ... by default the response format from a <delete> command does not change if you upgrade from solr 1.1 to 1.2 (nor does the response from any of hte opther update commands) if however you change your solrconfig.xml to register a handler using hte name "/update" then the response format will change depending on which RequestHandler you use ... the SOlr 1.2 example solrconfig.xml uses XmlUpdateRequestHandler which does have a different response format -- but this is explicitly pointed out in the 1.2 CHANGES.txt. In short: if you use solrconfig.xml that worked with Solr 1.1, SOlr 1.2 will behave exactly the same way ... if you change your solrconfig.xml to take advantage of the 1.2 features, then Solr will behave differently. : "tag" values... I am not using version number in URL for <delete> POSTs... : Thanks In 1.1 there was no reason to, because the XMLResponseWriter wasn't used when dealing with /udpate requests ... but in 1.2 you might want to if you register a RequestHandler with the name "/update" (and don't explicitly specify a response writer like json). That way you'll be protected from any future enhancements to the XMLResponseWriter's output format on update requests just like on query requests. -Hoss
