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
To simplify your workflow, you can register an externally hosted model using a connector in one of the connector blueprint formats. If you do so, a predefined model interface for this connector is generated automatically during model registration. The predefined model interface is generated based on the connector blueprint and the model's metadata, so you must strictly follow the blueprint when creating the connector in order to avoid errors.
The first thing I'm wondering, is what does it mean to "strictly follow the blueprint" and what can be changed/customized in the blueprint, in order to still trigger the automatic interface generation?
Secondly, is there a library of suggested/preset model interfaces?
An example of the ambiguity and issues I'm facing: the second connector example here has a request body containing parameters.prompt but not parameters.inputs anywhere. Yet the default interface generated from this requires inputs but not prompt.
Error when executing predict (not surprising, since prompt is needed in the request body and not listed under the default parameters in the connector blueprint)
{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "Some parameter placeholder not filled in payload: prompt"
}
],
"type": "illegal_argument_exception",
"reason": "Some parameter placeholder not filled in payload: prompt"
},
"status": 400
}
The automatically generated interfaces should be consistent & dependent on the connector blueprints' required parameters, such as to not cause added confusion when inputs satisfy the model interface, yet fail when hitting the actual prediction.
The text was updated successfully, but these errors were encountered:
I've run into inconsistencies in the documentation and functionality of the model interfaces.
The documentation states:
The first thing I'm wondering, is what does it mean to "strictly follow the blueprint" and what can be changed/customized in the blueprint, in order to still trigger the automatic interface generation?
Secondly, is there a library of suggested/preset model interfaces?
An example of the ambiguity and issues I'm facing: the second connector example here has a request body containing
parameters.prompt
but notparameters.inputs
anywhere. Yet the default interface generated from this requiresinputs
but notprompt
.Interface generated:
Error when executing predict (not surprising, since prompt is needed in the request body and not listed under the default
parameters
in the connector blueprint)The automatically generated interfaces should be consistent & dependent on the connector blueprints' required parameters, such as to not cause added confusion when inputs satisfy the model interface, yet fail when hitting the actual prediction.
The text was updated successfully, but these errors were encountered: