cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Machine Learning
Dive into the world of machine learning on the Databricks platform. Explore discussions on algorithms, model training, deployment, and more. Connect with ML enthusiasts and experts.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Migrated model to Unity catalog not seeing referenced serving endpoint

fbs342
Visitor

There was a model which was migrated from workspace model registry to unity catalog. At the time of initial creation of that model, dependencies to other databricks serving endpoints were configured using "DatabricksServiceEndpoint" config in mlflow. Note that this model regsitered on workspace model registry was placed on a serving endpoint called serving_a. 

After migration to unity catalog, when I attempt to place the unity catalog model as model on the serving endpoint serving_a, I get the error that it cannot find dependent serving endpoints which were setup when the model was created on workspace model registry. 

Please how can i solve this

2 REPLIES 2

SP_6721
Honored Contributor

Hi @fbs342 ,

Try pointing MLflow to the Unity Catalog registry in your deploy code with mlflow.set_registry_uri("databricks-uc"), then update serving_a to reference the UC model before redeploying the endpoint. After that, move any dependencies you previously configured via DatabricksServiceEndpoint into serving endpoint environment variables, read those values in your model code, and redeploy serving_a

fbs342
Visitor

The registry URI was already "databricks-uc" when workspace model registry was used. When I update the serving_a to reference UC model it works, its when I redeploy that the error I previously mentioned appears

 

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local communityโ€”sign up today to get started!

Sign Up Now