Insufficient Permissions Error when trying to access table #1555
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dakinggg
approved these changes
Sep 26, 2024
dakinggg
approved these changes
Sep 27, 2024
added 2 commits
September 27, 2024 12:35
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To resolve this when permissions thrown by spark are not properly wrapped.
Instead of regex every variant of security perm errors, it's a lot easier to just rewarp the errors thrown by spark. Three scenerios were manually tested and passed:
User doesn't have access to catalog
User doesn't have access to schema (but has access for catalog)
User doesn't have SELECT for table (has access to catalog + schema)
This way, it's a lot easier to catch the permission spark errors.