-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Re-deprecate xpack rollup endpoints #36451
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
Conversation
)"" This reverts commit 61c2db5.
…d cluster (elastic#36000)"" This reverts commit 40c5445.
When we cleanup the rollup in a cluster containing 6.x nodes we need to use `/_xpack/rollup` instead of `/_rollup` because the 6.x nodes don't know about `/_rollup`. In those cases we must ignore the deprecation warnings that the 7.0 node will return for the end point. Closes elastic#36044
Pinging @elastic/es-analytics-geo |
@jasontedor I see that you made non- |
Yes please, sorry for the conflicts. |
Will do! Conflicts happen. |
So now that I've merged this I'm not sure that I need the warnings work.... Let me check if I can drop that. |
Yes indeed. I can just revert all of that. We don't need it now. |
@elasticmachine test this please |
@Override | ||
public String getName() { | ||
return "rollup_delete_job_action"; | ||
return "delete_rollup_job"; |
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.
I've noticed a few of these changes that came along with my unrevert. Are these changes compatible with a mixed version cluster?
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.
That's a good question... I'm not sure. I don't really know how REST request names are used (or if they are just for display/task purposes?)
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.
They are used in the usage API, and ultimately intended to be surfaced in telemetry. In the long run, I want to open a change to derive the name from the class name and remove all these overrides, so in these changes I have been aligning these with that intended change, and removing "xpack" from the names in places where they exist. I am not worried about BWC during a rolling upgrade.
final Request getRollupJobRequest = new Request("GET", "_xpack/rollup/job/" + rollupJob); | ||
final Request getRollupJobRequest; | ||
if (isRunningAgainstOldCluster()) { | ||
getRollupJobRequest = new Request("GET", "/_xpack/rollup/job/" + rollupJob); |
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.
These are required because we can do a full cluster restart against versions that don't have the new endpoint.
This is ready for review so I've removed |
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.
Looks good. Sorry about the deprecation work/unwork; it didn't occur to me until looking at the problems that the security and ML work that we had another way to approach this that could be cleaner and avoid the difficulties we were initially trying to work around here.
We're going to need to do some work on deprecation when we go to remove the old APIs in master. But we should have the tools that we need for that already available then so it'll be easier. |
We don't write anything and the cleanup isn't compatible.
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.
LGTM, although I'm not sure about your question re: names. Left a question/comment about the rolling restart tests.
|
||
* {ref}/rollup-get-rollup-caps.html[GET /_xpack/rollup/data/<index_pattern+++>/_rollup_caps+++]: Get Rollup Capabilities | ||
* {ref}/rollup-get-rollup-caps.html[GET /_rollup/data/<index_pattern+++>/_rollup_caps+++]: Get Rollup Capabilities | ||
* {ref}/rollup-get-rollup-index-caps.html[GET /<index_name+++>/_rollup/data/+++]: Get Rollup Index Capabilities |
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.
Heh, accidental typo becomes the correct endpoint XD
@Override | ||
public String getName() { | ||
return "rollup_delete_job_action"; | ||
return "delete_rollup_job"; |
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.
That's a good question... I'm not sure. I don't really know how REST request names are used (or if they are just for display/task purposes?)
|
||
// create the rollup job | ||
final Request createRollupJobRequest = new Request("PUT", "/_xpack/rollup/job/rollup-id-test"); | ||
final Request createRollupJobRequest = new Request("PUT", "/_rollup/job/rollup-id-test"); |
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.
I'm not entirely sure how rolling upgrade tests pick their versions, but couldn't we go from < 6.6
to >= 6.6, <7.0
? In which case we'll need an assumeTrue()
on this test, or some kind of version check on these URIs?
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.
The rolling upgrade tests only go through the wire compatible versions so this should be safe.
Thank you @nik9000! |
I'm glad our intake build went green and I could get it merged! Thanks for
the review!
…On Tue, Dec 11, 2018, 20:03 Jason Tedor ***@***.*** wrote:
Thank you @nik9000 <https://github.com/nik9000>!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#36451 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANLol9FSys8kD3ncomWq8GXL1ucfrFeks5u4FXDgaJpZM4ZMExL>
.
|
Redeprecates the
/_xpack/rollup
endpoints in favor of/_rollup
.When we cleanup the rollup in a cluster containing 6.x nodes we need to
use
/_xpack/rollup
instead of/_rollup
because the 6.x nodes don'tknow about
/_rollup
. In those cases we must ignore the deprecationwarnings that the 7.0 node will return for the end point.
Closes #36044