You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The descriptions for "Model Ready" and "Model Metadata" in both the REST and gRPC specifications claim that the model version is optional. Is this true? If so, the specification should report it's optionality in more than a comment/description (optional in proto3 and required: false in openAPI). If the version is optional in the REST protocol, should there instead be another versionless route instead of eg, '/v2/models/${MODEL_NAME}/versions/${MODEL_VERSION}/ready'?
description: The “model ready” health API indicates if a specific model is ready for inferencing. The model name and (optionally) version must be available in the URL. If a version is not provided the server may choose a version based on its own policies.
description: 'The per-model metadata endpoint provides information about a model. A model metadata request is made with an HTTP GET to a model metadata endpoint. In the corresponding response the HTTP body contains the [Model Metadata Response JSON Object](#model-metadata-response-json-object) or the [Model Metadata Response JSON Error Object](#model-metadata-response-json-error-object). The model name and (optionally) version must be available in the URL. If a version is not provided the server may choose a version based on its own policies or return an error.'
The text was updated successfully, but these errors were encountered:
The descriptions for "Model Ready" and "Model Metadata" in both the REST and gRPC specifications claim that the model version is optional. Is this true? If so, the specification should report it's optionality in more than a comment/description (
optional
in proto3 andrequired: false
in openAPI). If the version is optional in the REST protocol, should there instead be another versionless route instead of eg,'/v2/models/${MODEL_NAME}/versions/${MODEL_VERSION}/ready'
?open-inference-protocol/specification/protocol/open_inference_grpc.proto
Lines 68 to 70 in eeb043e
open-inference-protocol/specification/protocol/open_inference_grpc.proto
Lines 98 to 100 in eeb043e
open-inference-protocol/specification/protocol/open_inference_rest.yaml
Line 61 in eeb043e
open-inference-protocol/specification/protocol/open_inference_rest.yaml
Line 104 in eeb043e
The text was updated successfully, but these errors were encountered: