Describe the bug
With the Unity Catalog explorer built into the extension now, viewing a Volume offers the same Open in Databricks option as tables, but when you try to open the Volume it takes you to a "table" referenced by the name of your volume and fails.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Unity Catalog'
- Click on a catalog and schema where the volume exists
- Click on a volume
- Click on 'Open in Databricks' button
- See object that doesn't exist (unless you have a table by the same name; and that's possible?)
Additional context
Specifically, it's trying to route to a table like
https://<workspace>.azuredatabricks.net/explore/data/<catalog>/<schema>/<asset>
When the volume object actually is
https://<workspace>.azuredatabricks.net/explore/data/volumes/<catalog>/<schema>/<asset>
Describe the bug
With the Unity Catalog explorer built into the extension now, viewing a Volume offers the same Open in Databricks option as tables, but when you try to open the Volume it takes you to a "table" referenced by the name of your volume and fails.
To Reproduce
Steps to reproduce the behavior:
Additional context
Specifically, it's trying to route to a table like
https://<workspace>.azuredatabricks.net/explore/data/<catalog>/<schema>/<asset>When the volume object actually is
https://<workspace>.azuredatabricks.net/explore/data/volumes/<catalog>/<schema>/<asset>