[
https://issues.apache.org/jira/browse/SOLR-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595843#comment-15595843
]
ASF subversion and git services commented on SOLR-9676:
-------------------------------------------------------
Commit 91f58ac72b603bc9a66f537829c0f99dcd65fbff in lucene-solr's branch
refs/heads/master from [~dsmiley]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=91f58ac ]
SOLR-9676: DefaultSolrHighlighter: clarify warning when FVH can't be used
> FastVectorHighligher log message could be improved
> --------------------------------------------------
>
> Key: SOLR-9676
> URL: https://issues.apache.org/jira/browse/SOLR-9676
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: highlighter
> Affects Versions: 4.10.4
> Reporter: Mike
> Assignee: David Smiley
> Priority: Minor
>
> If you try to use the FastVectorHighlighter on a field that doesn't have
> TermPositions and TermOffsets enabled, you get an ok error message:
> {{WARN org.apache.solr.highlight.DefaultSolrHighlighter – Solr will use
> Highlighter instead of FastVectorHighlighter because assignedTo field does
> not store TermPositions and TermOffsets.}}
> If you heed that message, and dutifully add TermPositions and TermOffsets to
> your schema, you get a crashing message that says:
> {code:none}
> Blah, blah, stacktrace
> ....
> Caused by: java.lang.IllegalArgumentException: cannot index term vector
> offsets when term vectors are not indexed (field="court")
> ...
> {code}
> Can we update the first message to say:
> {{Solr will use Highlighter instead of FastVectorHighlighter because
> assignedTo field does not store TermPositions, TermOffsets, and TermVectors.}}
> That'd save at least one headache next time I screw this up...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
