Hi Hoss,
Thanks for replying. I have created a jira:
https://issues.apache.org/jira/browse/SOLR-5697
It contains the required configs (actually a shard) and a query parser
maven project. These illustrate the issue.
I had to omit the solr.war from the webapps of the shard as it exceeded the
upload limit. Hope it is not a problem for you to fetch and deploy that.
Please let me know, if the jira is any clearer or if more detail is needed.
Thanks,
Dmitry
On Wed, Feb 5, 2014 at 2:58 AM, Chris Hostetter <hossman_luc...@fucit.org>wrote:
>
> : > 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.
> ...
> : 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.
>
> Dimitry: I'm having a really hard time wrapping my head arround what
> exactly you are describing.
>
> can you please either:
> 1) open a jira issue containing a patch with a test that demonstrates the
> problem
> 2) describe in detail the minimum steps someone (like me) would need to
> take in order to reproduce your problem -- either including a full set of
> configs & data, or some instructions on how to modify the sample configs /
> data
>
> (ie: if the bug only reproduces with multiple cores, then maybe some
> instructions on what changes to make to the configs
> in solr/example/multicore, and then what data to load, and what deletes to
> run, etc..)
>
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
--
Dmitry
Blog: http://dmitrykan.blogspot.com
Twitter: twitter.com/dmitrykan
