The solution (or workaround?) is to drop the defType from one of the cores
and use {!qparser} local param on every query, including the delete by
query. It would be really great, if this could be handled on the solr
config side only without involving the client changes.On Mon, Feb 3, 2014 at 4:02 PM, Dmitry Kan <solrexp...@gmail.com> wrote: > This exception is similar to what is talked about here: > https://gist.github.com/mbklein/6367133 > http://irc.projecthydra.org/2013-08-28.html > > We found out that: > > 1. this happens iff on two cores inside the same container there is a > query parser defined via defType. > 2. After removing index files on one of the cores, the delete by query > works just fine. Right after restarting the container, the same query fails. > > > Is there a jira for this? Should I create one? > > Dmitry > > > On Mon, Feb 3, 2014 at 2:03 PM, Dmitry Kan <solrexp...@gmail.com> wrote: > >> Hello! >> >> We are hitting a really strange and nasty issue when trying to delete by >> query and not when just adding documents. The exception says: >> http://pastebin.com/B1x5dAF7 >> >> Any ideas as to what is going on? >> >> The delete by query is referencing the unique field. The core's index >> does not contain the value that is being deleted. >> Solr: 4.3.1. >> >> >> -- >> Dmitry >> Blog: http://dmitrykan.blogspot.com >> Twitter: twitter.com/dmitrykan >> > > > > -- > Dmitry > Blog: http://dmitrykan.blogspot.com > Twitter: twitter.com/dmitrykan > -- Dmitry Blog: http://dmitrykan.blogspot.com Twitter: twitter.com/dmitrykan
