https://issues.apache.org/jira/browse/SOLR-5163
On Thu, Aug 15, 2013 at 6:04 PM, Steven Bower wrote:
> @Yonik that was exactly the issue... I'll file a ticket... there def
> should be an exception thrown for something like this..
>
> It would seem to me that eating any sort of exception is a re
@Yonik that was exactly the issue... I'll file a ticket... there def should
be an exception thrown for something like this..
It would seem to me that eating any sort of exception is a really bad
thing...
steve
On Thu, Aug 15, 2013 at 5:59 PM, Yonik Seeley wrote:
> I can reproduce something li
I can reproduce something like this by specifying a field that doesn't
exist for a "qf" param.
This seems like a bug... if a field doesn't exist, we should throw an
exception (since it's a parameter error not related to the "q" string where
we avoid throwing any errors).
-Yonik
http://lucidworks.c
If something causes an exception when edismax has called the basic Lucene
query parser, edismax will eat the exception, escape operators (your "AND")
and reparse, where your "AND" then gets treated as a simple term.
Maybe some difficulty in your field type analyzer?
We need to see your full qu
