I don't know if this is your issue, but in 1.2, we unified the response
format for /update and /select
Check the last paragraph in CHANGES.txt on "Upgrading from Solr 1.1"
To get the old behavior, make sure there is nothing in solrconfig.xml
mapped to "/update"
Fuad Efendi wrote:
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
"tag" values... I am not using version number in URL for <delete> POSTs...
Thanks
-----Original Message-----
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 19, 2007 1:11 AM
To: [email protected]
Subject: Re: Broken Backward Compatibility
: The only problem is changed protocols, old client application does not
: understand new XML responses from server. It recalls some very old
Can you elaborate on what "XML responses" have changed for you? To the
best of my knowledge any solrconfig.xml that worked with Solr 1.1 will
continue to work with 1.2 and provide the same XML response for updates
commands.
The XmlResponseWriter for queries supports a version param to ensure that
even if it changes overtime, you can always get the response format you
expect -- but i don't think it had a version bump in Solr 1.2
-Hoss
