- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2023 11:50 AM
@ah0896 it worked when using a workspace level shell scipt file and pointing to its path with workspace scope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2023 01:23 PM
@Anonymous @Retired_mod can anyone form databricks confirm on above issue please, there seems to be bit conflict on using custom scripts support on shared access mode cluster with unity catalog enabled please
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2023 01:41 AM
I'm very interested as well! If not possible, then very curious what is the best practice of installing cluster wide custom libraries on shared access mode clusters with unity catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2025 08:41 PM
Hello all,
Below workaround was efficient to me
1) pyodbc-install.sh is uploaded in a Volume
2) the shared cluster is able to navigate to the Volume to select the init script
3) the Databricks runtime is 15.4 LTS
4) the Allowlist has been updated to allow the init script
5) the cluster spins up with no problem
6) the pyodbc==5.2.0 library has been installed (although it made no difference) but
If you are using from ADF use below volumes option and provide ADF SP access to volume path