-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Add deprecation info API entries for deprecated monitoring settings #78799
Add deprecation info API entries for deprecated monitoring settings #78799
Conversation
Pinging @elastic/es-data-management (Team:Data Management) |
We typically target the master branch for deprecations and then backport to the branch where the deprecation will first take effect. In some cases, the deprecated feature will then be removed from the master branch but we're increasingly using longer deprecation periods in which case the deprecated feature will remain deprecated even in the master branch. |
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.
Code changes LGTM
Thanks for the explanation @danhermann. |
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.
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Outdated
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Outdated
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Outdated
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Outdated
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Outdated
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Show resolved
Hide resolved
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 agree with the patterns James suggested for the case where there are multiple settings. Had one question about the breaking changes entry--it contradicts itself. :-)
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Outdated
Show resolved
Hide resolved
...eprecation/src/test/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecksTests.java
Outdated
Show resolved
Hide resolved
The `xpack.monitoring.exporters.*.use_ingest` property was deprecated in 7.16.0 and | ||
has been removed. This parameter controlled the creation of pipelines for monitoring | ||
indices that previously had no function. | ||
The `xpack.monitoring.exporters.*.use_ingest` property was deprecated in 7.16.0. This |
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.
Is this setting going to be removed in 8.0, or after 8.0? The entry says it's removed, the Details say it will be removed. If it's only deprecated, I don't think we should include it in the breaking changes.
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 similar ambiguous documentation of "index.template.create_legacy_templates" (a deprecation info message for it was added in this PR, but the documentation has been ambiguous for a while).
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 updated the header text. A lot of this is all messed up because we made a recent course correction to not remove these settings in 8.0. So much copy pasta to clean up.
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.
If they are going to remain deprecated, I think we can just doc them as deprecated in 7.16 and omit them from the 8.0 breaking changes. The typical pattern is to only include newly-deprecated things, not repeat everything that's been previously deprecated.
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.
If they are going to remain deprecated, I think we can just doc them as deprecated in 7.16 and omit them from the 8.0 breaking changes.
+1. Let's remove these from 8.0. However, we'll still need to update the 7.16 deprecation docs to remove references to an 8.0 removal.
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.
Looks good to me, although I share @debadair's slight confusion about the documentation.
The `xpack.monitoring.exporters.*.use_ingest` property was deprecated in 7.16.0 and | ||
has been removed. This parameter controlled the creation of pipelines for monitoring | ||
indices that previously had no function. | ||
The `xpack.monitoring.exporters.*.use_ingest` property was deprecated in 7.16.0. This |
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 similar ambiguous documentation of "index.template.create_legacy_templates" (a deprecation info message for it was added in this PR, but the documentation has been ambiguous for a while).
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 deprecation info API changes LGTM. However, as @debadair pointed out, we should remove the 8.0 breaking changes docs. Instead, we should update the 7.16 deprecations to update any 8.0 removal references, probably as a separate PR.
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.
LGTM. Thanks for removing the docs.
@elasticmachine update branch |
* upstream/master: (24 commits) Implement framework for migrating system indices (elastic#78951) Improve transient settings deprecation message (elastic#79504) Remove getValue and getValues from Field (elastic#79516) Store Template's mappings as bytes for disk serialization (elastic#78746) [ML] Add queue_capacity setting to start deployment API (elastic#79433) [ML] muting rest compat test issue elastic#79518 (elastic#79519) Avoid redundant available indices check (elastic#76540) Re-enable BWC tests TEST Ensure password 14 chars length on Kerberos FIPS tests (elastic#79496) [DOCS] Temporarily remove APM links (elastic#79411) Fix CCSDuelIT for skipped shards (elastic#79490) Add other time accounting in HotThreads (elastic#79392) Add deprecation info API entries for deprecated monitoring settings (elastic#78799) Add note in breaking changes for nameid_format (elastic#77785) Use 'migration' instead of 'upgrade' in GET system feature migration status responses (elastic#79302) Upgrade lucene version 8b68bf60c98 (elastic#79461) Use Strings#EMPTY_ARRAY (elastic#79452) Quicker shared cache file preallocation (elastic#79447) [ML] Removing some code that's obsolete for 8.0 (elastic#79444) Ensure indexing_data CCR requests are compressed (elastic#79413) ...
Recently we have deprecated a number of settings in monitoring. These settings should be represented in the deprecation info API. This PR will be backported with some minor changes to the 7.x branch so that we can start the deprecation process in that release cycle.
Related issues:
#77659
#78564