-
Notifications
You must be signed in to change notification settings - Fork 835
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
Prediction API get model version #244
Comments
We certainly want to add a set of default fields taken from the resource definition such as image name and version. This work we need feedback on what people want by default. The wrappers at present focus on allowing the user to just return the predictions but we need to make it easy to pass back arbitrary meta data. Perhaps we can use this issue as a basis for what we would like to see. |
Image name and version would be sufficient for me. |
Great! Thank you. |
@cliveseldon trying to test this, I'm using the image |
You need to use images from 0.2.4-SNAPSHOT when installing seldon-core. Can you check you are using these. And you have redownloaded if so as they are SNAPSHOT images and recreated periodically. |
@cliveseldon This was working last week, but today I reinstalled seldon-core-0.2.4-SNAPSHOT, but it is returning the old format. |
@cliveseldon sorry, just realised that it picked up some old jar file from cache when installed. Works ok now. |
* make secret optional * make bucket name configurable * initial structure * Metrics docs * add example dashboard * add a list of tests * performance tests * add more docs * add a note about custom k6 image building
I have a single model deployment which I am planning to update occasionally. Just wondering if there is a way for the prediction API to return the model version that it is currently serving, as it can be ambiguous during a rolling update. Currently it only returns an empty header:
'meta': {'puid': 'lt91ru9u5f8j8530m9dl40rrqo', 'tags': {}, 'routing': {}}}
The text was updated successfully, but these errors were encountered: