Previously it was a requirement of the close job API that if the job had an associated datafeed that that datafeed was stopped before the job could be closed. Experience has shown that this is just a pedantic nuisance. If a user closes the job without first stopping the datafeed then it's just a mistake, and they then have to make two further calls, to stop the datafeed and then attempt to close the job again. This PR changes the behaviour so that if you ask to close a job whose datafeed is running then the datafeed gets stopped first as part of the same call. Datafeeds are stopped with the same level of force as the job close request specified. |
||
---|---|---|
.. | ||
anomaly-detection | ||
df-analytics/apis | ||
images | ||
ml-shared.asciidoc |