Unity Catalog - Error getting sample data in data explorer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2023 02:07 AM
I get an error message saying I Error getting sample data, when I try to view sample data from a table in a schema I created in a Unity Catalog. I dropped the schema and table and got a collague to recreate and still the same message. We are both Unity Catlog Admins and he is not recieving this error and can see the sample data. Even when we drop and recreate in his name its the same issues...............I can see the data if I actual query it within the sql section. I believe it may be a permissions issue.........but it appears that we have identical permissions. Any help would be greatful.
I have added a screen shot of the error
- Labels:
-
Data Explorer
-
Unity Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2025 08:58 AM
It’s likely a permissions or session issue; try checking table-level ACLs, refreshing your session, or verifying role inheritance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 07:36 PM
It sounds like a common issue with access control that can arise in database management systems or applications with user permissions. Checking table-level ACLs (Access Control Lists) is a great first step, as it ensures that the user has the proper permissions to access or modify the data. Refreshing your session can also help if there have been recent changes to permissions or roles that haven't been applied yet. Lastly, verifying role inheritance is crucial, as it determines if a user is properly inheriting permissions from their assigned roles. Addressing these areas should help resolve the access issue effectively!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Check your table level ACLs, refresh your session, and verify role inheritance. Even if permissions look the same, there might be a small difference causing the issue. Try comparing your access settings with your colleague’s to spot any discrepancies.


- « Previous
-
- 1
- 2
- Next »