You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Koji Sekiguchi (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/11/07 08:25:52 UTC

[jira] [Issue Comment Edited] (SOLR-1926) add hl.q parameter

    [ https://issues.apache.org/jira/browse/SOLR-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145240#comment-13145240 ] 

Koji Sekiguchi edited comment on SOLR-1926 at 11/7/11 7:25 AM:
---------------------------------------------------------------

I misunderstood Hoss's suggestion as I read it too fast. hl.text should be multiValued and its value should be analyzed.

{quote}
would it make more sense to imagine a multivalued "hl.text" param, such that each value is passed to the analyzer for each "hl.fl" field, and the resulting terms are all highlighted (in their respective fields) ... thus bypassing the complications of extracting temrs from queries?

would that be more useful or less useful?
{quote}

I like the idea! But as doHighlighting() method takes Query, it needs quite some time to implement it. I'd like to open a separate ticket for it.
                
      was (Author: koji):
    I misunderstood Hoss's suggestion as I read it too fast. hl.text should be multiValued and its value should be analyzed.

{quote}
would it make more sense to imagine a multivalued "hl.text" param, such that each value is passed to the analyzer for each "hl.fl" field, and the resulting terms are all highlighted (in their respective fields) ... thus bypassing the complications of extracting temrs from queries?

would that be more useful or less useful?
{quote}

I like the idea! But as doHighlighting() method takes Query, it is not easy. I'd like to open a separate ticket for it.
                  
> add hl.q parameter
> ------------------
>
>                 Key: SOLR-1926
>                 URL: https://issues.apache.org/jira/browse/SOLR-1926
>             Project: Solr
>          Issue Type: Improvement
>          Components: highlighter
>    Affects Versions: 1.4
>            Reporter: Koji Sekiguchi
>            Assignee: Koji Sekiguchi
>            Priority: Trivial
>             Fix For: 3.5, 4.0
>
>         Attachments: SOLR-1926.patch, SOLR-1926.patch, SOLR-1926.patch
>
>
> If hl.q parameter is set, HighlightComponent uses it rather than q.
> Use case:
> You search "PC" with highlight and facet capability:
> {code}
> q=PC
> &facet=on&facet.field=maker&facet.field=something
> &hl=on&hl.fl=desc
> {code}
> You get a lot of results with snippets (term "PC" highlighted in desc field). Then you click a link "maker:DELL(50)" to narrow the result:
> {code}
> q=PC
> &facet=on&facet.field=something
> &fq=maker:DELL
> &hl=on&hl.fl=desc
> {code}
> You'll get narrowed result with term "PC" highlighted snippets. But, sometimes I'd like to see "DELL" to be highlighted as well, because I clicked "DELL". In this case, hl.q can be used:
> {code}
> q=PC
> &facet=on&facet.field=something
> &fq=maker:DELL
> &hl=on&hl.fl=desc&*hl.q=PC+maker:DELL*
> {code}
> Note that hl.requireFieldMatch should be false (false is default) in this scenario.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org