Remove unfreeze REST endpoint #119227
Merged
Remove unfreeze REST endpoint #119227
Conversation
This file contains 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
PeteGillinElastic
force-pushed
the
remove-freeze-unfreeze-9.0
branch
3 times, most recently
from
e75badb to
5d0c861
Compare
PeteGillinElastic
added
>breaking
:Data Management/Indices APIs
|
Hi @PeteGillinElastic, I've created a changelog YAML for you. Note that since this PR is labelled |
PeteGillinElastic
force-pushed
the
remove-freeze-unfreeze-9.0
branch
from
f0b6d78 to
9dad9c1
Compare
mattkime
added a commit
to elastic/kibana
that referenced
this pull request
Jan 8, 2025
## Summary Remove code related to unfreezing indices since the functionality is being removed from v9 due to elastic/elasticsearch#119227
crespocarlos
pushed a commit
to crespocarlos/kibana
that referenced
this pull request
Jan 8, 2025
## Summary Remove code related to unfreezing indices since the functionality is being removed from v9 due to elastic/elasticsearch#119227
PeteGillinElastic
force-pushed
the
remove-freeze-unfreeze-9.0
branch
from
9dad9c1 to
7fc0815
Compare
This adds a sentence to `redirects.asciidoc` explaining what frozen indices were - otherwise, everything will point to the message about the unfreeze API having gone away, which is not very helpful. Some cross-references are updated to point to this rather than to the notice about the removal of the unfreeze API.
PeteGillinElastic
force-pushed
the
remove-freeze-unfreeze-9.0
branch
from
7fc0815 to
8d7d3cb
Compare
elasticsearchmachine
added
the
Team:Data Management
|
Pinging @elastic/es-data-management (Team:Data Management) |
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Jan 13, 2025
## Summary Remove code related to unfreezing indices since the functionality is being removed from v9 due to elastic/elasticsearch#119227
dakrone
approved these changes
Jan 13, 2025
| @@ -1,67 +0,0 @@ | |||
| { | |||
| "indices.unfreeze":{ | |||
There was a problem hiding this comment.
I have no idea how the clients spec handles removals, but we should maybe check there also after this is merged?
There was a problem hiding this comment.
Yeah, good point. I believe that the change will get automatically mirrored to https://github.com/elastic/elasticsearch-specification/tree/main/specification/_json_spec. That may cause validation errors which I guess would be solved by also removing https://github.com/elastic/elasticsearch-specification/tree/main/specification/indices/unfreeze.
martijnvg
pushed a commit
to martijnvg/elasticsearch
that referenced
this pull request
Jan 14, 2025
This adds a sentence to `redirects.asciidoc` explaining what frozen indices were - otherwise, everything will point to the message about the unfreeze API having gone away, which is not very helpful. Some cross-references are updated to point to this rather than to the notice about the removal of the unfreeze API. ES-9736 #comment Removed `_unfreeze` REST endpoint in elastic#119227
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
N.B. There is cleanup work we can do as a follow-up, but this is the main user-visible change.