[SOLR-1105] Use a different stored field for highlighting

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: highlighter
• Assignee: David Smiley
• Reporter: Dmitry Lihachev
• Created: 08/Apr/09 04:28
• Updated: 29/Mar/22 11:06

Description

DefaultSolrHighlighter uses stored field content to highlight. It has some disadvantages, because index grows up fast when using multilingual indexing due to several fields has to be stored with same content. This patch allows DefaultSolrHighlighter to use "contentField" attribute to loockup content in external field.

Excerpt from old schema:

<field name="title" type="text" stored="true" indexed="true" />
<field name="title_ru" type="text_ru" stored="true" indexed="true" />
<field name="title_en" type="text_en" stored="true" indexed="true" />
<field name="title_de" type="text_de" stored="true" indexed="true" />

The same after patching, highlighter will now get content stored in "title" field

<field name="title" type="text" stored="true" indexed="true" />
<field name="title_ru" type="text_ru" stored="false" indexed="true" contentField="title"/>
<field name="title_en" type="text_en" stored="false" indexed="true" contentField="title"/>
<field name="title_de" type="text_de" stored="false" indexed="true" contentField="title"/>

Issue Links

• is duplicated by: SOLR-5276 highlighter working using stemmed tokens from another field and text from another
• is related to: SOLR-16111 hl.queryFieldPattern support (advanced alternative to hl.requireFieldMatch)
• requires: LUCENE-7768 UnifiedHighlighter: Use a different stored field, possibly shared