-
Notifications
You must be signed in to change notification settings - Fork 42
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
[FEATURE] Shared mode/User Isolation option for job clusters #96
Labels
enhancement
New feature or request
Comments
aseemanand
changed the title
[FEATURE] Shared mode by default for job clusters
[FEATURE] Shared mode/User Isolation option for job clusters
Feb 9, 2024
Related to #31. Will take a look at this. |
6 tasks
This is resolved. Thanks @stikkireddy @asingamaneni |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is currently a permission issue for shared mode/user isolation for job clusters while using Brickflow. Per Databricks, local_disk0/.ephemeral_nfs is a directory used internally by the system, and users typically don't have direct access to it in shared cluster mode.
Important note:
Spark cannot directly interact with workspace files on compute configured with shared access mode, the purpose of this cluster is being secured, the action the import is trying to do is not allowed.
Reference: https://docs.databricks.com/en/files/workspace-interact.html#read-data-workspace-files
Cloud Information
Describe the solution you'd like
Job cluster successfully working with Shared mode/User isolation mode in Brickflow.
Describe alternatives you've considered
We gave SELECT on all referenced tables and views in Single User mode to avoid Databricks limitation. This incurs tech debt as it means any new table/view in the upstream source can break our data pipeline .
Additional context
None
The text was updated successfully, but these errors were encountered: