-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Deprecate freeze index API #72618
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
Merged
danhermann
merged 23 commits into
elastic:master
from
danhermann:70192_deprecate_freeze_endpoint
May 27, 2021
Merged
Deprecate freeze index API #72618
Changes from 13 commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
ff7d46a
deprecate freeze index endpoint
danhermann 2cd71df
fix some tests
danhermann 8896e3f
more test fixes
danhermann c2cca27
fix another test
danhermann 5755c03
checkstyle
danhermann 0a54e53
really fix checkstyle
danhermann eeb285f
fix sql tests
danhermann b713d0e
Merge branch 'master' into 70192_deprecate_freeze_endpoint
elasticmachine 71d2240
fix another test
danhermann 5e71390
DRY up test fix
danhermann 5d91f97
spotless!
danhermann 85212ad
fix another one
danhermann 240683e
arg
danhermann 29f0955
changes allowed_warnings to warnings
danhermann 100f159
skip docs test
danhermann f89f11b
Merge branch 'master' into 70192_deprecate_freeze_endpoint
elasticmachine 5d0aa4a
skip more docs tests
danhermann 25238c7
skip one more
danhermann b7c22ca
disable failing REST compatibility tests
danhermann 924f7f5
Merge branch 'master' into 70192_deprecate_freeze_endpoint
danhermann 6e01aa2
Merge branch 'master' into 70192_deprecate_freeze_endpoint
elasticmachine 4ce37a1
also deprecate unfreeze endpoint
danhermann 1170101
fix some tests
danhermann File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,8 @@ | ||
--- | ||
"Basic": | ||
- skip: | ||
features: [ "allowed_warnings" ] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should this be "warnings" instead of "allowed_warnings" ? The difference is that if you only allow, then the warning can be missing and still pass the test. "warnings" is more like "require_warnings" |
||
|
||
- do: | ||
index: | ||
index: test | ||
|
@@ -12,6 +15,8 @@ | |
body: { "foo": "Hello: 2" } | ||
|
||
- do: | ||
allowed_warnings: | ||
- "Frozen indices are deprecated because they provide no benefit given improvements in heap memory utilization. They will be removed in a future release." | ||
indices.freeze: | ||
index: test | ||
|
||
|
@@ -51,6 +56,8 @@ | |
|
||
|
||
- do: | ||
allowed_warnings: | ||
- "Frozen indices are deprecated because they provide no benefit given improvements in heap memory utilization. They will be removed in a future release." | ||
indices.freeze: | ||
index: test* | ||
|
||
|
@@ -102,6 +109,8 @@ | |
- "the default value for the ?wait_for_active_shards parameter will change from '0' to 'index-setting' in version 8; specify '?wait_for_active_shards=index-setting' to adopt the future default behaviour, or '?wait_for_active_shards=0' to preserve today's behaviour" | ||
|
||
- do: | ||
allowed_warnings: | ||
- "Frozen indices are deprecated because they provide no benefit given improvements in heap memory utilization. They will be removed in a future release." | ||
indices.freeze: | ||
index: test*,not_available | ||
ignore_unavailable: true | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 should also deprecate this endpoint, because it will also technically be going away. If we don't show the message a user could hit this a bunch but not know it's going away.
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 was operating off the deprecation schedule listed in the meta issue in which
unfreeze
deprecation happens in 8.0. I'm open to deprecating it earlier though I'd like to get buy-in from at least some others involved in the meta issue.Uh oh!
There was an error while loading. Please reload this page.
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.
@zuketo, could you weigh in on the question of deprecating theunfreeze
endpoint now versus in 8.0?Edit: scratch that. We'll sort it out among the team.