Skip to content

Fix internal link in migration guide #79489

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.

Sign up for GitHub

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
merged 2 commits into from
Oct 19, 2021
Merged

Fix internal link in migration guide #79489

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f440b63
Fix internal link in migration guide
DaveCTurner Oct 19, 2021
be000e8
Remove repeated word
DaveCTurner Oct 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/reference/migration/migrate_7_16.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -277,14 +277,14 @@ use only persistent settings.
[%collapsible]
====
*Details* +
The <<cluster-health>> API includes options for waiting for certain health
conditions to be satisfied. If the requested conditions are not satisfied
within a timeout then {es} will send back a normal response including the field
`"timed_out": true`. In earlier versions it would also use the HTTP response
code `408 Request timeout` if the request timed out, and `200 OK` otherwise.
The `408 Request timeout` response code is not appropriate for this situation
and its use is deprecated. Future versions will use the response code `200 OK`
for both cases.
The {ref}/cluster-health.html[cluster health API] includes options for waiting
for certain health conditions to be satisfied. If the requested conditions are
not satisfied within a timeout then {es} will send back a normal response
including the field `"timed_out": true`. In earlier versions it would also use
the HTTP response code `408 Request timeout` if the request timed out, and `200
OK` otherwise. The `408 Request timeout` response code is not appropriate for
this situation and its use is deprecated. Future versions will use the response
code `200 OK` for both cases.

*Impact* +
Update your application to read the `"timed_out"` field of the response instead
Expand Down