lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Updated] (SOLR-5564) hl.maxAlternateFieldLength should apply to original field when fallback field does not exist
Date Tue, 24 Dec 2013 00:24:51 GMT

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

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

    Summary: hl.maxAlternateFieldLength should apply to original field when fallback field
does not exist  (was: hl.maxAlternateFieldLength should apply to original field when fallback
is attempted)

> 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
>             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


Mime
View raw message