[NO_PARENT_EXTERNAL_LOCATION_FOR_PATH] When browsing our metastore default location

[mmenjivar]

Hi, as described in the title, when I try to explore the content of our metastore default location (external location created by default when the metastore is created) I get NO_PARENT_EXTERNAL_LOCATION_FOR_PATH. I've tried using a Serverless SQL warehouse and normal SQL warehouse with the same results. In addition I've tried to do an ls with dbutils in an interactive cluster running dbr 14.2 also with the same results. I have all permissions over the external location so I'm not sure if this is an expected behavior.

Trying to create a new external location using the same S3 bucket fails as expected because overlapping.

[kamal_ch]

The error NO_PARENT_EXTERNAL_LOCATION_FOR_PATH you are encountering is related to missing permissions for accessing the external location in Unity Catalog. This behavior is expected if the necessary permissions are not correctly set.

Here are the steps you can take to resolve this error:

• Grant READ FILES Permission:
    • Ensure that you have the READ FILES permission on the external location. This permission allows you to read files directly from your cloud object storage.
    • To grant this permission, use the following command:
   

sql
    GRANT READ FILES ON EXTERNAL LOCATION `<external location name>` TO <user/group>;
    

    • This can be done by the external location owner or metastore admins.

• Verify Ownership and Permissions:
    • Check the ownership of the external location using:
   

sql
    DESCRIBE EXTERNAL LOCATION <external location name>;
    

    • Review the current grants on the external location with:
   

sql
    SHOW GRANTS ON EXTERNAL LOCATION <external location name>;
    

• Fallback Mode:
    • Consider enabling fallback mode on external locations if you are in the process of migrating workloads and need to ensure uninterrupted access. This mode allows the system to fall back to existing cluster- or notebook-scoped credentials if Unity Catalog permissions are not sufficient.These steps should help resolve the permission-related issues you are facing with accessing the external location.