-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[BUG] _cat help content cleanup after fork #14653
Copy link
Copy link
Closed
Labels
OtherbugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomersv1.3.19Issues and PRs related to version 1.3.19Issues and PRs related to version 1.3.19v2.16.0Issues and PRs related to version 2.16.0Issues and PRs related to version 2.16.0v3.0.0Issues and PRs related to version 3.0.0Issues and PRs related to version 3.0.0
Description
Describe the bug
It seems that help output of the _cat API was not fully reviewed when the fork happened.
One example: http://localhost:9200/_cat/nodes?help
id | id,nodeId | unique node id
pid | p | process id
ip | i | ip address
port | po | bound transport port
http_address | http | bound http address
version | v | es version
type | t | es distribution type
build | b | es build hash
[... cont.]
See the explanation for version, type and build.
It would be useful to review all _cat API help texts.
Related component
Other
To Reproduce
- Go to
http://localhost:9200/_cat/ - Iterate over all options (ie.
allocation,segment_replication, ...) - Append
?helpto the URL - Check the
helptext, especially the explanation column
Expected behavior
Help output should not refer to previous product name or acronyms.
Additional Details
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
OtherbugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomersv1.3.19Issues and PRs related to version 1.3.19Issues and PRs related to version 1.3.19v2.16.0Issues and PRs related to version 2.16.0Issues and PRs related to version 2.16.0v3.0.0Issues and PRs related to version 3.0.0Issues and PRs related to version 3.0.0