bug? No highlighting results with dismax and q.alt=*:*

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

bug? No highlighting results with dismax and q.alt=*:*

Peter Wolanin-2
For the Drupal Apache Solr Integration module, we are exploring the
possibility of doing facet browsing  - since we are using dismax as
the default handler, this would mean issuing a query with an empty q
and falling back to to q.alt='*:*' or some other q.alt that matches
all docs.

However, I notice when I do this that we do not get any highlights
back in the results despite defining a highlight alternate field.

In contrast, if I force the standard request handler then I do get
text back from the highlight alternate field:

select/?q=*:*&qt=standard&hl=true&hl.fl=body&hl.alternateField=body&hl.maxAlternateFieldLength=256

However, I then loose the nice dismax features of weighting the
results using bq and bf parameters.  So, is this a bug or the intended
behavior?

The relevant fragment of the solrconfig.xml is this:

  <requestHandler name="partitioned" class="solr.SearchHandler" default="true">
    <lst name="defaults">
     <str name="defType">dismax</str>

     <str name="q.alt">*:*</str>

   <!-- example highlighter config, enable per-query with hl=true -->
     <str name="hl">true</str>
     <str name="hl.fl">body</str>
     <int name="hl.snippets">3</int>
     <str name="hl.mergeContiguous">true</str>
   <!-- instructs Solr to return the field itself if no query terms are
        found -->
     <str name="f.body.hl.alternateField">body</str>
     <str name="f.body.hl.maxAlternateFieldLength">256</str>


Full solrconfig.xml and other files:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/?pathrev=DRUPAL-6--1

--
Peter M. Wolanin, Ph.D.
Momentum Specialist,  Acquia. Inc.
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: bug? No highlighting results with dismax and q.alt=*:*

Peter Wolanin-2
Possibly this issue is related:  https://issues.apache.org/jira/browse/SOLR-825

Though it seems that might affect the standard handler, while what I'm
seeing is more sepcific to the dismax handler.

-Peter

On Thu, May 7, 2009 at 8:27 PM, Peter Wolanin <[hidden email]> wrote:

> For the Drupal Apache Solr Integration module, we are exploring the
> possibility of doing facet browsing  - since we are using dismax as
> the default handler, this would mean issuing a query with an empty q
> and falling back to to q.alt='*:*' or some other q.alt that matches
> all docs.
>
> However, I notice when I do this that we do not get any highlights
> back in the results despite defining a highlight alternate field.
>
> In contrast, if I force the standard request handler then I do get
> text back from the highlight alternate field:
>
> select/?q=*:*&qt=standard&hl=true&hl.fl=body&hl.alternateField=body&hl.maxAlternateFieldLength=256
>
> However, I then loose the nice dismax features of weighting the
> results using bq and bf parameters.  So, is this a bug or the intended
> behavior?
>
> The relevant fragment of the solrconfig.xml is this:
>
>  <requestHandler name="partitioned" class="solr.SearchHandler" default="true">
>    <lst name="defaults">
>     <str name="defType">dismax</str>
>
>     <str name="q.alt">*:*</str>
>
>   <!-- example highlighter config, enable per-query with hl=true -->
>     <str name="hl">true</str>
>     <str name="hl.fl">body</str>
>     <int name="hl.snippets">3</int>
>     <str name="hl.mergeContiguous">true</str>
>   <!-- instructs Solr to return the field itself if no query terms are
>        found -->
>     <str name="f.body.hl.alternateField">body</str>
>     <str name="f.body.hl.maxAlternateFieldLength">256</str>
>
>
> Full solrconfig.xml and other files:
> http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/?pathrev=DRUPAL-6--1
>
> --
> Peter M. Wolanin, Ph.D.
> Momentum Specialist,  Acquia. Inc.
> [hidden email]
>



--
Peter M. Wolanin, Ph.D.
Momentum Specialist,  Acquia. Inc.
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: bug? No highlighting results with dismax and q.alt=*:*

Marc Sturlese
I have experienced it before... maybe you can manage something similar to your q.alt using the params q and qf. Highlight will work in that case (I sorted it out doing that)
Peter Wolanin-2 wrote
Possibly this issue is related:  https://issues.apache.org/jira/browse/SOLR-825

Though it seems that might affect the standard handler, while what I'm
seeing is more sepcific to the dismax handler.

-Peter

On Thu, May 7, 2009 at 8:27 PM, Peter Wolanin <peter.wolanin@acquia.com> wrote:
> For the Drupal Apache Solr Integration module, we are exploring the
> possibility of doing facet browsing  - since we are using dismax as
> the default handler, this would mean issuing a query with an empty q
> and falling back to to q.alt='*:*' or some other q.alt that matches
> all docs.
>
> However, I notice when I do this that we do not get any highlights
> back in the results despite defining a highlight alternate field.
>
> In contrast, if I force the standard request handler then I do get
> text back from the highlight alternate field:
>
> select/?q=*:*&qt=standard&hl=true&hl.fl=body&hl.alternateField=body&hl.maxAlternateFieldLength=256
>
> However, I then loose the nice dismax features of weighting the
> results using bq and bf parameters.  So, is this a bug or the intended
> behavior?
>
> The relevant fragment of the solrconfig.xml is this:
>
>  <requestHandler name="partitioned" class="solr.SearchHandler" default="true">
>    <lst name="defaults">
>     <str name="defType">dismax</str>
>
>     <str name="q.alt">*:*</str>
>
>  
>     <str name="hl">true</str>
>     <str name="hl.fl">body</str>
>     <int name="hl.snippets">3</int>
>     <str name="hl.mergeContiguous">true</str>
>  
>     <str name="f.body.hl.alternateField">body</str>
>     <str name="f.body.hl.maxAlternateFieldLength">256</str>
>
>
> Full solrconfig.xml and other files:
> http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/?pathrev=DRUPAL-6--1
>
> --
> Peter M. Wolanin, Ph.D.
> Momentum Specialist,  Acquia. Inc.
> peter.wolanin@acquia.com
>



--
Peter M. Wolanin, Ph.D.
Momentum Specialist,  Acquia. Inc.
peter.wolanin@acquia.com
Reply | Threaded
Open this post in threaded view
|

Re: bug? No highlighting results with dismax and q.alt=*:*

Peter Wolanin-2
Well, in this case we want to match all documents, so I'm not sure
that can be accomplished with dismax other than using a q.alt ?

-Peter

On Fri, May 8, 2009 at 1:32 PM, Marc Sturlese <[hidden email]> wrote:

>
> I have experienced it before... maybe you can manage something similar to
> your q.alt using the params q and qf. Highlight will work in that case (I
> sorted it out doing that)
>
> Peter Wolanin-2 wrote:
>>
>> Possibly this issue is related:
>> https://issues.apache.org/jira/browse/SOLR-825
>>
>> Though it seems that might affect the standard handler, while what I'm
>> seeing is more sepcific to the dismax handler.
>>
>> -Peter
>>
>> On Thu, May 7, 2009 at 8:27 PM, Peter Wolanin <[hidden email]>
>> wrote:
>>> For the Drupal Apache Solr Integration module, we are exploring the
>>> possibility of doing facet browsing  - since we are using dismax as
>>> the default handler, this would mean issuing a query with an empty q
>>> and falling back to to q.alt='*:*' or some other q.alt that matches
>>> all docs.
>>>
>>> However, I notice when I do this that we do not get any highlights
>>> back in the results despite defining a highlight alternate field.
>>>
>>> In contrast, if I force the standard request handler then I do get
>>> text back from the highlight alternate field:
>>>
>>> select/?q=*:*&qt=standard&hl=true&hl.fl=body&hl.alternateField=body&hl.maxAlternateFieldLength=256
>>>
>>> However, I then loose the nice dismax features of weighting the
>>> results using bq and bf parameters.  So, is this a bug or the intended
>>> behavior?
>>>
>>> The relevant fragment of the solrconfig.xml is this:
>>>
>>>  <requestHandler name="partitioned" class="solr.SearchHandler"
>>> default="true">
>>>    <lst name="defaults">
>>>     <str name="defType">dismax</str>
>>>
>>>     <str name="q.alt">*:*</str>
>>>
>>>   <!-- example highlighter config, enable per-query with hl=true -->
>>>     <str name="hl">true</str>
>>>     <str name="hl.fl">body</str>
>>>     <int name="hl.snippets">3</int>
>>>     <str name="hl.mergeContiguous">true</str>
>>>   <!-- instructs Solr to return the field itself if no query terms are
>>>        found -->
>>>     <str name="f.body.hl.alternateField">body</str>
>>>     <str name="f.body.hl.maxAlternateFieldLength">256</str>
>>>
>>>
>>> Full solrconfig.xml and other files:
>>> http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/?pathrev=DRUPAL-6--1
>>>
>>> --
>>> Peter M. Wolanin, Ph.D.
>>> Momentum Specialist,  Acquia. Inc.
>>> [hidden email]
>>>
>>
>>
>>
>> --
>> Peter M. Wolanin, Ph.D.
>> Momentum Specialist,  Acquia. Inc.
>> [hidden email]
>>
>>
>
> --
> View this message in context: http://www.nabble.com/bug--No-highlighting-results-with-dismax-and-q.alt%3D*%3A*-tp23438048p23450189.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>



--
Peter M. Wolanin, Ph.D.
Momentum Specialist,  Acquia. Inc.
[hidden email]