We don't always want to use the dismax handler in our setup.
Doug
Yonik Seeley wrote:
On Jan 21, 2008 9:06 PM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
We've found a way to work around it. In our search components, we're doing
something like:
defType = defType == null ? DisMaxQParserP
On Jan 21, 2008 9:06 PM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
> We've found a way to work around it. In our search components, we're doing
> something like:
>
>defType = defType == null ? DisMaxQParserPlugin.NAME : defType;
Would it be easier to just add it as a default parameter in t
We've found a way to work around it. In our search components, we're doing
something like:
defType = defType == null ? DisMaxQParserPlugin.NAME : defType;
If you add &defType=dismax to the query string, it'll use the
DisMaxQParserPlugin.
Unfortunately, I haven't been able to figure out an
The QueryComponent supports both lucene queryparser syntax and dismax
query syntax.
The dismax request handler now simply sets defType (the default base
query type) to "dismax"
-Yonik
On Jan 21, 2008 1:23 PM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
> Is there any support for DisMax (or any se
On Jan 21, 2008 10:23 AM, Doug Steigerwald
<[EMAIL PROTECTED]> wrote:
> Is there any support for DisMax (or any search request handlers) in search
> components, or is that
> something that still needs to be done? It seems like it isn't supported at
> the moment.
I was curious about this, too ..
