[
https://issues.apache.org/jira/browse/SOLR-10153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890544#comment-15890544
]
Amrit Sarkar commented on SOLR-10153:
-------------------------------------
Alright :) Yes, +1 for the suggestion. I hate long worded arguments and just
_seperator_ is meaningful and apt. CustomSeparatorBreakIterator itself is
naming the char '_seperator_' in its implementation.
Regarding using string as separator in near future, looking at the
CustomSeparatorBreakIterator's code, it seems it can be done with not much
effort. I will give it a shot soon.
We should go with: *hl.bs.type=SEPARATOR with e.g. hl.bs.separator=|*
> UnifiedSolrHighlighter support for CustomSeparatorBreakIterator (LUCENE-6485)
> -----------------------------------------------------------------------------
>
> Key: SOLR-10153
> URL: https://issues.apache.org/jira/browse/SOLR-10153
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: highlighter
> Reporter: Amrit Sarkar
> Attachments: SOLR-10153.patch, SOLR-10153.patch,
> SOLR_10153_UH_and_PH_hl_customSeparatorChar.patch
>
>
> Lucene 5.3 added a CustomSeparatorBreakIterator (see LUCENE-6485)
> UnifiedSolrHighlighter should support *CustomSeparatorBreakIterator* along
> with existing ones, WholeBreakIterator etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
