Make client auto choose prediction endpoint #425
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Will close #400
Problem
We use to have to manually specify
prediction_path
toClient
for either/prediction
or/anomaly/prediction
Solution
Now that we are returning
422
status code if the model being served is not an AnomalyDetector, the client can default to/anomaly/prediction
and when it gets a422
can update itsprediction_path
to/prediction
instead for all future requests.