New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fast Vector Highlighter does no work with nested field as target #80895
Comments
Pinging @elastic/es-search (Team:Search) |
I'm running into this problem when trying to upgrade Elasticsearch 7.11 to 7.16. A lot of highlighting stuff in our project breaks due to this. The problem is not only for nested fields, or any particular query (like in #82458), but to subfields in general. I have done some investigation and it started in 7.14 and is still the same in 8.0.0. I've reproduced it with these steps:
Like mentioned by OP adding @cbuescher do you know if this is getting any attention? Or will be getting any attention any time soon? |
…lastic#85815) FVH was relying on `SourceLookup.extractRawValues()` to load its data, but this no longer works for multifields. It should instead use value fetchers which will correctly locate the input for multifields and/or copy fields. Fixes elastic#84690 Fixes elastic#82458 Fixes elastic#80895 Fixes elastic#75011
Elasticsearch version (
bin/elasticsearch --version
): 7.15.2Plugins installed: []
JVM version (
java -version
): the one included in ESOS version (
uname -a
if on a Unix-like system): Windows 10Description of the problem including expected versus actual behavior:
When using a nested field as target for Fast Vector Highligter no result is produced. (This works fine with the Unified Highlighter).
The problem seems to be that fvh tries to read the target field literally from the source and as this would not be present in the source
it assumes that the field is absent. If the nested field has
store: true
set everything works as expected as it then reads the stored field instead of visiting the source-object.The reason for using a nested field as target is that the root-field is a date-field and we then have multiple nested fields with different versions of the date-string with
with_positions_offsets
enabled forterm_vector
.Steps to reproduce:
make a search like the following with and without
store:true
enabled in the mapping of the the nested target field (date.text
).The text was updated successfully, but these errors were encountered: