[
https://issues.apache.org/jira/browse/LUCENE-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396156#comment-15396156
]
David Smiley commented on LUCENE-7397:
--------------------------------------
Sorry I'm not clear what specifically you propose.
FYI, perhaps related: the Lucene default term vector implementation/codec will
load term vectors for all fields, even if you are actually only interested in
fewer. It's easy to accidentally re-decode all term vectors when code asks for
just one. I don't know if the FVH has this problem or not. I know the default
highlighter can benefit from term vectors and it does not suffer from this
potential trap.
> Inefficient FVhighlighting when set many HighlightedField.
> ----------------------------------------------------------
>
> Key: LUCENE-7397
> URL: https://issues.apache.org/jira/browse/LUCENE-7397
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/highlighter
> Environment: CentOS release 6.4 (Final)
> quad core 1.87
> 8gb memory
> tested Elasticsearch - 1.5 with lucene 4.10.4
> But i see mirrored Master version in github
> https://github.com/apache/lucene-solr
> Reporter: donghyun Kim
> Priority: Minor
>
> when highlighting, search result
> org.apache.lucene.search.vectorhighlight.FastVectorHighlighter.java
> getBestFragment method ~ FieldTermStack.java read whole doc's termvector
> every highlighted field.
> It causes slow query when many highlight field
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
