Makes sense, thanks. One more question. Shouldn't there be a mechanism to
define a default query parser?
something like (inside QParserPlugin):
public static String DEFAULT_QTYPE = "default"; // now it
is LuceneQParserPlugin.NAME;
public static final Object[] standardPlugins = {
DEFAULT_QTYPE, LuceneQParserPlugin.class,
LuceneQParserPlugin.NAME, LuceneQParserPlugin.class,
...
}
in this way we can use solrconfig.xml to override the default qparser
Or does that break some assumptions?
roman
On Wed, Apr 17, 2013 at 8:34 AM, Yonik Seeley <yo...@lucidworks.com> wrote:
> On Tue, Apr 16, 2013 at 9:44 PM, Roman Chyla <roman.ch...@gmail.com>
> wrote:
> > Is there some profound reason why the defType is not passed onto the
> filter
> > query?
>
> defType is a convenience so that the main query parameter "q" can
> directly be the user query (without specifying it's type like
> "edismax").
> Filter queries are normally machine generated.
>
> -Yonik
> http://lucidworks.com
>
