Lucene’s unified highlighter will concatenate all the snippets into one string by default. For example if we have a multivalued field with:

"The quick brown fox jumps right over the little lazy dog",
"This string mentions a dog"

Applying a unified highlighter to it will result in:

"The quick brown fox jumps right over the little lazy <em>dog</em>This string mentions a <em>dog</em>"

While using other highlighter types, or if using the Elasticsearch backend, the result will be:

"The quick brown fox jumps right over the little lazy <em>dog</em>",
"This string mentions a <em>dog</em>"

To get Lucene’s unified highlighter to behave in the same way, we’d need to have our custom implementation of both PassageFormatter and FieldHighlighter

Alternatively, we might end up simply exposing the ellipsis parameter of the DefaultPassageFormatter to the users through Lucene-specific unified highlighter DSL.