petrcv-db
petrcv-db
Apparently, in a legacy workspace it's possible to have a job with no owner: ``` { "object_id": "/jobs/803387", "object_type": "job", "access_control_list": [ { "group_name": "admins", "all_permissions": [ { "permission_level": "CAN_MANAGE",...
When importing users I get the following error that fails the whole import pipeline ``` post: https://wehkamp-play-ground.cloud.databricks.com/api/2.0/preview/scim/v2/Users Get: https://wehkamp-play-ground.cloud.databricks.com/api/2.0/preview/scim/v2/Users 2022-04-08,09:58:05;INFO;Creating user: [email protected] Traceback (most recent call last): File "migrate/migration_pipeline.py", line...
`migration_pipeline.py` doesn't include importing and exporting ML Flow objects (`mlflow_experiments, mlflow_experiments_permissions, mlflow_runs`). They should be added or at least it should be documented that these have to be migrated separately...
When I run the migration pipeline on a workspace that contains a job with an outdated expression, that won't run anymore, the whole pipeline fails with an error: ``` 2022-04-25,14:17:54;DEBUG;https://xxx-play-ground.cloud.databricks.com:443...
When exporting notebooks I got the following error: ``` {"error_code": "RESOURCE_DOES_NOT_EXIST", "message": "Path (/Development/Buy-Alongs_dev/sets_poc/siamese/0_make_features (1)) doesn't exist.", "http_status_code": 404, "path": "/Development/Buy-Alongs_dev/sets_poc/siamese/0_make_features (1)"} ``` Checking the source workspace there's no notebook...
The migration tool package should start tracking its dependencies using something like a Pipfile or Poetry. I just spent quite some time figuring out I need to update to urllib3...