You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2014/01/03 09:43:54 UTC

[jira] [Assigned] (SOLR-5564) hl.maxAlternateFieldLength should apply to original field when fallback field does not exist

     [ https://issues.apache.org/jira/browse/SOLR-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Høydahl reassigned SOLR-5564:
---------------------------------

    Assignee: Jan Høydahl

> hl.maxAlternateFieldLength should apply to original field when fallback field does not exist
> --------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5564
>                 URL: https://issues.apache.org/jira/browse/SOLR-5564
>             Project: Solr
>          Issue Type: Bug
>          Components: highlighter
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>             Fix For: 5.0, 4.7, 4.6.1
>
>         Attachments: SOLR-5564.patch
>
>
> For a customer we use {{f.body.hl.alternateField=teaser&hl.maxAlternateFieldLength=100}}
> But some articles do not have the teaser field filled at all, so for queries that do not match the body, we get the full huge body returned in the frontend.
> If the highlighter has tried to fallback to the alternateField, then hl.maxAlternateFieldLength should always apply, even to text from the original field if alternateFIeld does not exist.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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