-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Fixed match only text block loader not working when a keyword multi field is present #134582
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
Changes from 4 commits
536d196
38a1220
545d546
757a4b4
fdfb970
a092a99
3bddfe6
752be91
254b1df
c4cd18b
280d444
132c8e9
c3a63e6
641a16d
3deefc5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
pr: 134582 | ||
summary: Fixed match only text block loader not working when a keyword multi field | ||
is present | ||
area: Mapping | ||
type: bug | ||
issues: [] |
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
|
@@ -528,6 +528,8 @@ tests: | |||
- class: org.elasticsearch.xpack.esql.ccq.MultiClusterSpecIT | ||||
method: test {csv-spec:fork.FiveFork} | ||||
issue: https://github.com/elastic/elasticsearch/issues/134560 | ||||
- class: org.elasticsearch.upgrades.MatchOnlyTextRollingUpgradeIT | ||||
issue: https://github.com/elastic/elasticsearch/issues/134097 | ||||
|
assumeTrue("requires storing leaf array offsets", oldClusterHasFeature("gte_v9.1.0")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
even if this is temporary? My idea was to mute this test now, backport the fix, and then unmute the test. Without that, the test will fail against previous versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The convention is to use a node feature for this. Tests are muted for genuine test failures.
So let's add a node feature for this (in MapperFeatures#getTestFeatures(...)
). The upside it is that the test can be back ported without having think about older versions not having this change (e.g. when changes to MatchOnlyTextRollingUpgradeIT
in this PR land in 8.19 branch).
Uh oh!
There was an error while loading. Please reload this page.