Hi, Shawn,
(Sorry, I have sent this your private email address...)
Thanks for your reply.
I understood what you are saying. However, at least, I think it strange
that UnifiedSolrHighlighter
returns the same error when choosing ", " as the field delimiter in
hl.fl (e.g. hl.fl=name,%20manu).
This is because UnifiedSolrHighlighter detects that there is a
zero-length string between "," and " ",
and treats the string as a field name.
Is this a correct behavior?
Thanks,
Yasufumi
On 2017/09/05 12:21 AM, Shawn Heisey wrote:
On 9/3/2017 10:31 PM, Yasufumi Mizoguchi wrote:
I am testing UnifiedHighlighter(hl.method=unified) with Solr 6.6 and
found that the highlighter returns following error when hl.fl
parameter has undefined fields.
The error occurs even if hl.fl parameter has ", "(<COMMA> + <SPACE>)
as a field delimiter. (e.g. hl.fl=name, manu)
Is this a bug? I think that the highlighter should set OffsetSource as
"NONE_NEEDED", if fields are not available....
I think Solr is doing exactly what it should in this instance. If you
ask Solr to use a field that it doesn't have, immediately returning an
error message is the right thing to do. If Solr were to ignore the
error and proceed with the request anyway, then the person making the
request might never know that they have made a mistake.
Thanks,
Shawn
