-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Remove X-Pack centric graph endpoints #36010
Conversation
This commit is part of our plan to deprecate and ultimately remove the use of _xpack in the REST APIs.
Pinging @elastic/es-search |
"path": "/{index}/_xpack/graph/_explore", | ||
"paths": ["/{index}/_xpack/graph/_explore", "/{index}/{type}/_xpack/graph/_explore"], | ||
"path": "/{index}/_xpack/_graph/explore", | ||
"paths": ["/{index}/_xpack/_graph/explore", "/{index}/{type}/_xpack/_graph/explore"], | ||
"parts" : { |
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.
Remove the _xpack
?
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.
@markharwood Oops, thanks! I pushed a2dc134.
Do the yaml tests now need a "skip" marker for <7.0 versions now that we changed the endpoint? Presumably the BWC tests would fail if a 7.x client sends to a 6.x cluster? |
@markharwood Yeah, I pushed 8118f03. |
LGTM. Kibana Graph UI has a small label in the "last request" spy that shows the URL used for the graph call - I can change that. |
This commit is part of our plan to deprecate and ultimately remove the use of _xpack in the REST APIs.
Relates #35958