[
https://issues.apache.org/jira/browse/LUCENE-7768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959459#comment-15959459
]
David Smiley commented on LUCENE-7768:
--------------------------------------
Thanks for contributing this Julien. I'm looking at the patch on SOLR-1105:
* needs a test; but maybe wait until we like the API...
* You introduced a {{Function<String,String>}} to do the mapping but I think
{{UnaryOperator<String>}} is more correct. But regardless of that, I think
instead of those, it could be done with an over-rideable method accepting the
input logical stored field and returning the desired _actual_ stored field.
The highlightFieldsAsObjects method could call it. It would be nice if
loadFieldValues & LimitedStoredFieldVisitor required no modifications...
leaving all the work to highlightFieldsAsObjects which can up front decide the
unique set of fields to be fetch and keep this once.
> Use a different stored field for highlighting
> ---------------------------------------------
>
> Key: LUCENE-7768
> URL: https://issues.apache.org/jira/browse/LUCENE-7768
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/highlighter
> Reporter: Julien Martin
>
> UnifiedHighlighter 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.
> Lucene portion of issue SOLR-1105, initially raised on Solr
> See https://issues.apache.org/jira/browse/SOLR-1105
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
