-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find Usage of DBFS Mounts in the Workspace and Repo #391
Labels
feat/crawler
migrate/code
Abstract Syntax Trees and other dark magic
migrate/jobs
Step 5 - Upgrading Jobs for External Tables
migrate/volumes
migrate from raw DBFS mounts to UC Volumes
Comments
3 tasks
nfx
added
enhancement
New feature or request
to be discussed
feat/crawler
step/assessment
go/uc/upgrade - Assessment Step
labels
Oct 6, 2023
Functional Requirements
Persisted Tablemount_path_usages
Implementation Details
Considerations
|
1 task
nfx
added
migrate/volumes
migrate from raw DBFS mounts to UC Volumes
migrate/jobs
Step 5 - Upgrading Jobs for External Tables
and removed
enhancement
New feature or request
to be discussed
feat/cli
CLI commands
labels
Apr 22, 2024
26 tasks
nfx
changed the title
Find Usage of Mount Points in the Workspace and Repo
Find Usage of DBFS Mounts in the Workspace and Repo
Apr 22, 2024
Duplicate of #1133 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feat/crawler
migrate/code
Abstract Syntax Trees and other dark magic
migrate/jobs
Step 5 - Upgrading Jobs for External Tables
migrate/volumes
migrate from raw DBFS mounts to UC Volumes
Historically, customers have used mount points to connect their Databricks workspaces to their chosen cloud object storage, and many chose to utilize file paths as opposed to tables for accessing their data. For these long-time customers, the migration process is extremely manual, slow, and disruptive. This drastically decreases the chances of legacy customers upgrading their environment to Unity Catalog, which over time will lead to increased customer churn in favor of other platforms which do not require such a manual refactoring. Until now, we have not been able to provide an easier path forward for these customers.
The text was updated successfully, but these errors were encountered: