Skip to content

Fix doc to remove outdated note about fine-grained access control support #1983

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eric-maynard merged 1 commit into from
Jul 1, 2025
Merged

Fix doc to remove outdated note about fine-grained access control support #1983

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions site/content/in-dev/unreleased/access-control.md
View file
Open in desktop

@eric-maynard eric-maynard Jul 1, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few other issues in this doc, such as the fact that a Policy is now a valid securable object, and the note that If you update the privileges bestowed to a service principal, the updates won't take effect for up to one hour.. I also think the diagram at the bottom is confusing at best.

However, this change by itself looks good enough to merge as it's just not accurate.

@cgpoh cgpoh Jul 1, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @eric-maynard for your review. Maybe a separate PR to fix the other issues? Actually, the diagram together with the example help me when trying to understand the RBAC :)

Original file line number Diff line number Diff line change
Expand Up @@ -103,10 +103,6 @@ This section describes the privileges that are available in the Polaris access c
roles are granted to principal roles, and principal roles are granted to service principals to specify the operations that service principals can
perform on objects in Polaris.

> [!IMPORTANT]
> You can only grant privileges at the catalog level. Fine-grained access controls are not available. For example, you can grant read
> privileges to all tables in a catalog but not to an individual table in the catalog.

To grant the full set of privileges (drop, list, read, write, etc.) on an object, you can use the *full privilege* option.

### Table privileges
Expand Down
Loading