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
I ran the MLflow connector externally following the steps at https://docs.open-metadata.org/latest/connectors/ml-model/mlflow/yaml , but I was unable to extract metadata for MLflow models managed on the Unity Catalog in the Databricks environment.
If I intentionally exclude the model in the filter conditions for the target model, the model on the Unity Catalog is displayed, so it seems that the existence of the model is recognized. Also, I was able to extract metadata for MLflow models not managed by Unity Catalog on Databricks without any problems.
Does this mean that the MLflow connector does not support models managed by Unity Catalog?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I ran the MLflow connector externally following the steps at https://docs.open-metadata.org/latest/connectors/ml-model/mlflow/yaml , but I was unable to extract metadata for MLflow models managed on the Unity Catalog in the Databricks environment.
If I intentionally exclude the model in the filter conditions for the target model, the model on the Unity Catalog is displayed, so it seems that the existence of the model is recognized. Also, I was able to extract metadata for MLflow models not managed by Unity Catalog on Databricks without any problems.
Does this mean that the MLflow connector does not support models managed by Unity Catalog?
Beta Was this translation helpful? Give feedback.
All reactions