Closed premjayaraj closed 1 year ago
This a limitation of the Databricks API where cannot import a notebook revision. You can export a notebook revision but you cannot link it to the imported run.
See https://github.com/mlflow/mlflow-export-import#importing-notebooks.
Databricks API doesn't allow you to import and attach a notebook revision to an MLflow run.
Customer have used this repo https://github.com/mlflow/mlflow-export-import, to migrate from ST shard to E2.
When they are trying to access the source notebook from MLflow tracking UI it is redirecting to the ST shard.