Releases: vespa-engine/pyvespa
Releases · vespa-engine/pyvespa
Version 0.11.0
- Use
tasks
instead ofmodels
as argument name forModelServer
to align with the fact this argument takes instances of typeTextTask
. - Use
model_id
instead ofmodel_name
to identify a model sincemodel_id
is what we use when defining a Task.
Version 0.10.0
Introduce stateless model evaluation with SequenceClassification task.
- Adapt
ApplicationPackage
to allow for simpler configurations, e.g. no schema. - Implement
ModelServer
, which is a simplifiedApplicationPackage
focused on stateless model evaluation. ApplicationPackage
is now included on theVespa
instance when deploying apps with pyvespa.- This helps to process input/output involved when using stateless model evaluations through
app.predict
.
- This helps to process input/output involved when using stateless model evaluations through
Vespa
now hasget_model_endpoint
andpredict
to use for stateless model evaluation mode.- Both
VespaDocker
andVespaCloud
now work withModelServer
deployment to deploy stateless model evaluation apps. - Created
SequenceClassification
task that inherits from the base classTextTask
.
Version 0.9.0
VespaDocker
and VespaCloud
are now only available via the vespa.deployment
module.
Version 0.8.1
VespaDocker
andVespaCloud
will move to the deployment module- v 0.8.1 still works with
vespa.package.VespaDocker
andvespa.package.VespaCloud
but it will issue a deprecation warning informing users to usevespa.deployment.VespaDocker
andvespa.deployment.VespaCloud
instead. - v 0.9.0 will remove
vespa.package.VespaDocker
andvespa.package.VespaCloud
and users must usevespa.deployment.VespaDocker
andvespa.deployment.VespaCloud
- v 0.8.1 still works with