Describe the feature:
Elasticsearch version (bin/elasticsearch --version): 7.3
Plugins installed: [icu]
JVM version (java -version): 9.0.1
OS version (uname -a if on a Unix-like system): Win10
Description of the problem including expected versus actual behavior:
Doing a phrase search with query_string e.g. on e.g. "alien resurrection" does not get highligted if graph_synonyms filter is enabled and the the synonym list contains multi term synonyms including one of the terms from the phrase search.
In some cases it seems to work partially:
Steps to reproduce:
Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.
search_analyzer and add a multi term synonym for "face hugger, alien"Provide logs (if relevant):
Pinging @elastic/es-search
@slumx thanks for your interest in elasticsearch. I doubt that this issue relates to the JVM version, but nevertheless, it could be good to double check that it reproduces on a supported JVM version.
My bad, it is running 1.8.0_152 (the included one)
Can you test with the unified highlighter ? It can also use terms_vector so the performance should be similar. The fast_vector highlighter is not actively maintained in Lucene and the unified highlighter was added to replace the old ones so it might be faster for you to switch to this new highlighter rather than waiting for a bug resolution.
Ok I will try that. The reason that I use FVH is that it seems to be the only highlighter which can combine fields analyzed with different analyzers into one field, isn't this still the case? (We use this feature a lot).
The reason that I use FVH is that it seems to be the only highlighter which can combine fields analyzed with different analyzers into one field, isn't this still the case? (We use this feature a lot).
This is not implemented yet which is the reason why we keep the fast_vector highlighter for now.
I'll try to reproduce the bug to see if the fix is simple.
Is there any possibility of supporting this in the future?
Most helpful comment
This is not implemented yet which is the reason why we keep the fast_vector highlighter for now.
I'll try to reproduce the bug to see if the fix is simple.