Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 25078D3AD for ; Wed, 3 Oct 2012 14:12:09 +0000 (UTC) Received: (qmail 11226 invoked by uid 500); 3 Oct 2012 14:12:07 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 11176 invoked by uid 500); 3 Oct 2012 14:12:07 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 11168 invoked by uid 99); 3 Oct 2012 14:12:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 14:12:07 +0000 Date: Thu, 4 Oct 2012 01:12:07 +1100 (NCT) From: "Yonik Seeley (JIRA)" To: dev@lucene.apache.org Message-ID: <754005550.159156.1349273527933.JavaMail.jiratomcat@arcas> In-Reply-To: <2106282844.130644.1348694107969.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (SOLR-3897) Preserve multi-value fields during hit highlighting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468580#comment-13468580 ] Yonik Seeley commented on SOLR-3897: ------------------------------------ bq. And I suppose this necessitates another array level in the response? I guess it depends on how widely applicable this feature is. If very few will have a need for it (which I think is the case?) we should try and keep it as unobtrusive as possible. > Preserve multi-value fields during hit highlighting > --------------------------------------------------- > > Key: SOLR-3897 > URL: https://issues.apache.org/jira/browse/SOLR-3897 > Project: Solr > Issue Type: Improvement > Components: highlighter > Reporter: Joel Bernstein > Assignee: Yonik Seeley > Priority: Minor > Fix For: 4.1 > > Attachments: SOLR-3897.patch, SOLR-3897.patch > > > The behavior of the default Solr hit highlighter on multi-value fields is to only return the values that have a hit and sort them by score. > This ticket supplies a patch that adds a new highlight parameter called "preserveMulti" which can be used on a feild by field basis to return all of the values in their original order. If this parameter is used, the values that have a hit are highlighted and the ones that do not contain a hit are returned un-highlighted. > The "preserveMulti" parameter works with the default standard highlighter and follows the standard highlighting conventions. > Sample usage for a field called "cat": > f.cat.hl.preserveMulti=true -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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