On Feb 22, 2007, at 1:54 AM, Chris Hostetter wrote:
: I believe now having SolrQueryParser set the operator based on the
: schema configuration is much more sensible.
I haven't looked at this in depth, but i *think* this breaks the
DisMaxQueryParser (i'm guessing AND isn't the default in our test
config)
Does DisjunctionMaxQueryParser require the operator to be AND? Does
it always need to be set one way or the other? If so, we could just
override that setting in the constructor, eh?
i remember discussing this before, and suggesting that SolrQueryParser
should use the schema only for understanding field types, so
calling the
basic constructor gives you a barebones SOlrQUeryParser; and any other
options (like default op) could be set in a utility/factory method.
http://www.nabble.com/QueryParser-default-operator---AND-
tf1977319.html#a5425365
Sure, the QueryParsing.parseQuery methods could set it, and I'll
change it if needed, but I want to understand how this breaks
DisjunctionMaxQueryParser first. Can q.op be set specifically for
the DisjunctionMaxQueryParser?
Thanks,
Erik
