Repository navigation
docs(acl): document permission-based object visibility - #597
Open
glasstiger wants to merge 7 commits into
Open
glasstiger wants to merge 7 commits into
glasstiger wants to merge 7 commits into
Conversation
|
🚀 Build success! Latest successful preview: https://preview-597--questdb-documentation.netlify.app/docs/ Commit SHA: 0cffdfb
|
QuestDB Enterprise 4.1.0 hides tables, views, materialized views, and live views from principals that hold no permission on them (questdb-enterprise#1248, questdb#7687). - Add an object visibility section to the RBAC page: visibility rules, protected and public tables, the metadata any permission discloses, the missing-object errors that replace Access denied, and the paths that still reveal an object exists. - Document the catalogue function restrictions for materialized and live views, and metadata functions inside views. - Note the SYSTEM ADMIN requirement of reader_pool(), writer_pool(), and hydrate_table_metadata(), and how wal_tables(), storage_policies, and table_cold_partitions() follow visibility. - Update GRANT, REVOKE, SHOW, DROP, and view statement error tables, the related cookbooks, and add a 4.1.0 upgrade checklist. - Correct the WITH VERIFICATION example, which checks the grantee, and state that only the built-in admin can grant on a missing table. - Add changelog entries and the 10.1.0 and 4.1.0 releases.
glasstiger
force-pushed
the
ia_hide_tables_without_access
branch
from
October 22, 2026 23:29
8de5686 to
61ddced
Compare
…t_access # Conflicts: # documentation/query/sql/show.md
This file contains hidden or 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
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.
Summary
Documents permission-based object visibility, which QuestDB Enterprise 4.1.0 introduced in https://github.com/questdb/questdb-enterprise/pull/1248 and its Open Source counterpart, questdb/questdb#7687. Principals no longer see the tables, views, materialized views, and live views they hold no permission on, and statements that name such an object fail like they do for a missing one.
DATABASE ADMIN,SYSTEM ADMIN, andON ALL TABLESgrants), protected and public tables, the metadata any permission discloses, a table of the missing-object errors that replaceAccess denied, the breaking change, and the paths that still reveal that an object exists.SHOWstatements in a view's definition read through the view's authority, objects substituted throughOVERRIDABLEvariables resolve as the reader, and tables named by table-name functions are now view dependencies.SHOWstatements count as catalogue functions, theSYSTEM ADMINrequirement for using them in a view's own query, their rejection through regular views, and the new errors.SYSTEM ADMINforreader_pool(),writer_pool(), andhydrate_table_metadata(), protected tables inwal_tables(), and visibility fortable_cold_partitions()andstorage_policies, including the 4.1.0 requirement forSELECTonsys.sp_entriesandsys.sp_links.GRANT,REVOKE,SHOW,DROP, and the view, materialized view, and live view statements.WITH VERIFICATIONexample claimed it checks the table, but it checks the grantee. Only the built-in admin can grant on a table that does not exist yet.Error messages and examples were checked on a running build of the 4.1.0 sources.
COPY PERMISSIONS, which the Enterprise PR also changes, has no reference page and is not covered.