-
Notifications
You must be signed in to change notification settings - Fork 25k
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
FVH Highlighter does not work with the inner hits properly #65533
Labels
>bug
:Search Relevance/Highlighting
How a query matched a document
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
Comments
henningandersen
added
the
:Search Relevance/Highlighting
How a query matched a document
label
Nov 30, 2020
Pinging @elastic/es-search (Team:Search) |
jtibshirani
added a commit
that referenced
this issue
Dec 9, 2020
This PR fixes a regression where fvh fragments could be loaded from the wrong document _source. Some `FragmentsBuilder` implementations contain a `SourceLookup` to load from _source. The lookup should be positioned to load from the current hit document. However, since `FragmentsBuilder` are cached and shared across hits, the lookup is never updated to load from the new documents. This means we accidentally load _source from a different document. The regression was introduced in #60179, which started storing `SourceLookup` on `FragmentsBuilder`. Fixes #65533.
Thanks a lot @babayotakun for raising this. A fix will be available in the upcoming releases 7.10.2 and 7.11. |
jtibshirani
added a commit
to jtibshirani/elasticsearch
that referenced
this issue
Dec 9, 2020
…5641) This PR fixes a regression where fvh fragments could be loaded from the wrong document _source. Some `FragmentsBuilder` implementations contain a `SourceLookup` to load from _source. The lookup should be positioned to load from the current hit document. However, since `FragmentsBuilder` are cached and shared across hits, the lookup is never updated to load from the new documents. This means we accidentally load _source from a different document. The regression was introduced in elastic#60179, which started storing `SourceLookup` on `FragmentsBuilder`. Fixes elastic#65533.
jtibshirani
added a commit
that referenced
this issue
Dec 10, 2020
This PR fixes a regression where fvh fragments could be loaded from the wrong document _source. Some `FragmentsBuilder` implementations contain a `SourceLookup` to load from _source. The lookup should be positioned to load from the current hit document. However, since `FragmentsBuilder` are cached and shared across hits, the lookup is never updated to load from the new documents. This means we accidentally load _source from a different document. The regression was introduced in #60179, which started storing `SourceLookup` on `FragmentsBuilder`. Fixes #65533.
jtibshirani
added a commit
to jtibshirani/elasticsearch
that referenced
this issue
Dec 10, 2020
…5641) This PR fixes a regression where fvh fragments could be loaded from the wrong document _source. Some `FragmentsBuilder` implementations contain a `SourceLookup` to load from _source. The lookup should be positioned to load from the current hit document. However, since `FragmentsBuilder` are cached and shared across hits, the lookup is never updated to load from the new documents. This means we accidentally load _source from a different document. The regression was introduced in elastic#60179, which started storing `SourceLookup` on `FragmentsBuilder`. Fixes elastic#65533.
jtibshirani
added a commit
that referenced
this issue
Dec 10, 2020
This PR fixes a regression where fvh fragments could be loaded from the wrong document _source. Some `FragmentsBuilder` implementations contain a `SourceLookup` to load from _source. The lookup should be positioned to load from the current hit document. However, since `FragmentsBuilder` are cached and shared across hits, the lookup is never updated to load from the new documents. This means we accidentally load _source from a different document. The regression was introduced in #60179, which started storing `SourceLookup` on `FragmentsBuilder`. Fixes #65533.
javanna
added
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
and removed
Team:Search
Meta label for search team
labels
Jul 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Search Relevance/Highlighting
How a query matched a document
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
Elasticsearch version: 7.10.0
Running in docker from image docker.elastic.co/elasticsearch/elasticsearch:7.10.0
Fvh highligher does not highlight actual content of the inner hit. It seems to alway returning highlight for the first relevant inner hit but with the highlight offsets of the current inner hit. Other highlighters ("plain" and "unified") are working correctly.
Steps:
Result:
Highlights are returned with the correct offsets and indents but with the wrong contents.
Should be world hello for the second inner hit.
The text was updated successfully, but these errors were encountered: