On Feb 22, 2007, at 4:50 PM, Chris Hostetter wrote:
i agree overplaning is bad ... i just want to ensure any current
users of
"new SolrQueryParser" aren't suprised to find the behavior changing
out
from under them -- any future changes for more pluggable query parsers
will probably affect the existing RequestHandlers -- but the role of
SolrQueryParser as a simple subclass of Lucene's QueryParser that
knows
about field types should generally remain true for a long time.
And the way a default of AND and the hype of DisMax queries
(something I intend to spend some time with ASAP, just haven't yet)
it should be a moot point. Setting it to AND would imply you're
likely using the standard request handler.
: Yeah, that looks good. A fair bit more tinkering than I envisioned,
: though it looks great.
I'll go ahead and commit (the really nice thing is that it makes more
schema configured query parser options easier to implement because
they
won't require a log of public accessors on the IndexSchema).
Nice. Thanks for the quick review and more complete fix.
Erik
