-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Remove IndexSettingDeprecatedInV7AndRemovedInV8 removal TODOs #119842
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
base: main
Are you sure you want to change the base?
Remove IndexSettingDeprecatedInV7AndRemovedInV8 removal TODOs #119842
Conversation
Index settings using this property have been marked for removal in v9, but we still need to support reading indices from v7 now (via the new N-2 read-only support policy), so we need to keep these settings around as well.
Pinging @elastic/es-search (Team:Search) |
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
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.
Since you are there, what about replacing the TODOs with @UpdateForV10
annotations, so they will be easier to find?
*/ | ||
@UpdateForV9(owner = UpdateForV9.Owner.CORE_INFRA) // introduce IndexSettingDeprecatedInV8AndRemovedInV9 to replace this constant | ||
@UpdateForV9(owner = UpdateForV9.Owner.CORE_INFRA) // introduce IndexSettingDeprecatedInV8AndRemovedInV9. |
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.
We have validation checking that a setting marked with this constant is used in an index created before v8. When introducing IndexSettingDeprecatedInV8AndRemovedInV9
(which will be needed, at least for the index.merge.policy.max_merge_at_once_explicit
setting), which IndexVersion
should be checked in this case? IndexVersions.UPGRADE_TO_LUCENE_10_0_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.
that's a good q. Technically, upgrade to lucene 10 is not yet 9.0. I would rather think that we should refer to a future index version that's tied to the actual removal of the index setting for v9? Or has that already happened?
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.
No, this hasn't happened yet, and I'm not sure when or which team will handle it. I just found a deprecated index setting with a comment referencing IndexSettingDeprecatedInV8AndRemovedInV9
. Adding those checks when the settings are actually removed sounds good - we'll just need a notification when that's planned
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.
I've added IndexSettingDeprecatedInV8AndRemovedInV9: #120334
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
Index settings using this property have been marked for removal in v9,
but we still need to support reading indices from v7 now (via the new
N-2 read-only support policy), so we need to keep these settings around as well.