Re: Highlighter throwing InvalidTokenOffsetsException for field with large number of synonyms

Yay! I'm glad the UnifiedHighlighter is serving you well. I was about to suggest it. If you think the fragmentation/snippeting could be improved in a general way then post a JIRA for consideration. Note: identical results with the original Highlighter is a non-goal. On Mon, Apr 23, 2018 at 10:

RE: Highlighter throwing InvalidTokenOffsetsException for field with large number of synonyms

Finally got back to looking at this, and found that the solution was to switch to the unified highlighter which doesn't seem to have the same problem with my complex synonyms. This required some tweaking of the

RE: Highlighter throwing InvalidTokenOffsetsException for field with large number of synonyms

David Yes, highlighting is tricky, especially with synonyms. Sorry, I would need to see a bit more of your config before saying more about it. Thanks -- Rick -- Sorry for being brief. Alternate email is rickleir at yahoo dot com

RE: Highlighter throwing InvalidTokenOffsetsException for field with large number of synonyms

Hi Rick, Thanks for your response. The reason that we do it like this is that the localities are also part of another indexed field that contains the entire address. We actually do the search over that field, and we are only using the highlighting on the problematic field so that we can tell

Re: Highlighter throwing InvalidTokenOffsetsException for field with large number of synonyms

David When you have "lcx__balmoral__cannum__clear_lake__lower_norton" in a field, would you search for *cannum* ? That might not perform well. Why not have a multivalue field for this information? It could be that you have a good reason for this, and I just do not understand. Cheers -- Rick --