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.com On Thu, Aug 15, 2013 at 5:19 PM, Steven Bower <smb-apa...@alcyon.net> wrote: > I have query like: > > q=foo AND bar > defType=edismax > qf=field1 > qf=field2 > qf=field3 > > with debug on I see it parsing to this: > > (+(DisjunctionMaxQuery((field1:foo | field2:foo | field3:foo)) > DisjunctionMaxQuery((field1:and | field2:and | field3:and)) > DisjunctionMaxQuery((field1:bar | field2:bar | field3:bar))))/no_coord > > basically it seems to be treating the AND as a term... any thoughts? > > thx, > > steve >
