2020-07-23 23:48:22 +08:00
|
|
|
[discrete]
|
2019-06-03 23:24:16 +08:00
|
|
|
[[breaking_80_rollup_changes]]
|
2021-01-15 01:14:48 +08:00
|
|
|
==== Rollup changes
|
2019-06-03 23:24:16 +08:00
|
|
|
|
|
|
|
|
//NOTE: The notable-breaking-changes tagged regions are re-used in the
|
|
|
|
|
//Installation and Upgrade Guide
|
|
|
|
|
|
|
|
|
|
//tag::notable-breaking-changes[]
|
2020-05-11 20:59:40 +08:00
|
|
|
.The StartRollupJob endpoint now returns a success status if a job has already started.
|
|
|
|
|
[%collapsible]
|
|
|
|
|
====
|
|
|
|
|
*Details* +
|
2019-06-03 23:24:16 +08:00
|
|
|
Previously, attempting to start an already-started rollup job would
|
|
|
|
|
result in a `500 InternalServerError: Cannot start task for Rollup Job
|
|
|
|
|
[job] because state was [STARTED]` exception.
|
|
|
|
|
|
|
|
|
|
Now, attempting to start a job that is already started will just
|
2020-05-11 20:59:40 +08:00
|
|
|
return a successful `200 OK: started` response.
|
|
|
|
|
|
|
|
|
|
*Impact* +
|
|
|
|
|
Update your workflow and applications to assume that a 200 status in response to
|
|
|
|
|
attempting to start a rollup job means the job is in an actively started state.
|
|
|
|
|
The request itself may have started the job, or it was previously running and so
|
|
|
|
|
the request had no effect.
|
2020-12-30 22:59:24 +08:00
|
|
|
====
|
2021-07-27 05:43:39 +08:00
|
|
|
// end::notable-breaking-changes[]
|
