Drop transport client from ping_schedule docs #89264
Merged
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
The docs for `transport.ping_schedule` note that the transport client defaults to a 5s ping schedule, but this is no longer relevant. This commit drops this from the docs, and also moves the docs for this setting further down the page to reflect its relative unimportance.
DaveCTurner
added
>docs
elasticsearchmachine
added
Team:Distributed (Obsolete)
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Aug 11, 2022
The docs for `transport.ping_schedule` note that the transport client defaults to a 5s ping schedule, but this is no longer relevant. This commit drops this from the docs, and also moves the docs for this setting further down the page to reflect its relative unimportance.
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Aug 11, 2022
The docs for `transport.ping_schedule` note that the transport client defaults to a 5s ping schedule, but this is no longer relevant. This commit drops this from the docs, and also moves the docs for this setting further down the page to reflect its relative unimportance.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Aug 11, 2022
The docs for `transport.ping_schedule` note that the transport client defaults to a 5s ping schedule, but this is no longer relevant. This commit drops this from the docs, and also moves the docs for this setting further down the page to reflect its relative unimportance.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Aug 11, 2022
The docs for `transport.ping_schedule` note that the transport client defaults to a 5s ping schedule, but this is no longer relevant. This commit drops this from the docs, and also moves the docs for this setting further down the page to reflect its relative unimportance.
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.
The docs for
transport.ping_schedulenote that the transport clientdefaults to a 5s ping schedule, but this is no longer relevant. This
commit drops this from the docs, and also moves the docs for this
setting further down the page to reflect its relative unimportance.