DisMax and Search Components

[Doug Steigerwald <ds...@mcclatchyinteractive.com>]

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.

We want to be able to use a field collapsing component 
(https://issues.apache.org/jira/browse/SOLR-236), but still be able to use our DisMax handlers.

Right now it's one or the other, and we -need- both.

Thanks.
doug

Re: DisMax and Search Components

[Yonik Seeley <yo...@apache.org>]

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
<ds...@mcclatchyinteractive.com> 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.
>
> We want to be able to use a field collapsing component
> (https://issues.apache.org/jira/browse/SOLR-236), but still be able to use our DisMax handlers.
>
> Right now it's one or the other, and we -need- both.
>
> Thanks.
> doug
>

Re: DisMax and Search Components

[Doug Steigerwald <ds...@mcclatchyinteractive.com>]

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
> <ds...@mcclatchyinteractive.com> 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 the request handler?
> 
> -Yonik

Re: DisMax and Search Components

[Yonik Seeley <yo...@apache.org>]

On Jan 21, 2008 9:06 PM, Doug Steigerwald
<ds...@mcclatchyinteractive.com> 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 the request handler?

-Yonik

Re: DisMax and Search Components

[Doug Steigerwald <ds...@mcclatchyinteractive.com>]

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 easy way to access the config for the different 
defined disxmax handlers in the config, so on our service side (Rails app), we're going to have a 
configuration with all the params we need to pass (qf, pf, fl, etc) and send them based on 
parameters we have coming into the service that we use to figure out which dismax handler to use 
(uh, yeah, I think that sounds right).

This may not be the best way to do it, but it will work fine for us until we can dedicate more time 
to it (we roll out Solr and our search service to QA next week).

Doug

Charles Hornberger wrote:
> On Jan 21, 2008 10:23 AM, Doug Steigerwald
> <ds...@mcclatchyinteractive.com> 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 ... If it *is* something that needs to
> be done, am happy to help w/ the coding. But I would need some
> advice/guidance up front --  I'm new enough to Solr that the design
> behind the SearchComponents refactoring is not immediately obvious to
> me, either from the Jira comments or the code itself.
> 
> -Charlie

Re: DisMax and Search Components

[Charles Hornberger <ch...@gmail.com>]

On Jan 21, 2008 10:23 AM, Doug Steigerwald
<ds...@mcclatchyinteractive.com> 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 ... If it *is* something that needs to
be done, am happy to help w/ the coding. But I would need some
advice/guidance up front --  I'm new enough to Solr that the design
behind the SearchComponents refactoring is not immediately obvious to
me, either from the Jira comments or the code itself.

-Charlie