-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql: the output of SHOW TENANT system WITH CAPABILITIES is nonsensical #98749
Copy link
Copy link
Closed
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual teamua-ux-papercutUX and OX bugs that would be GA blockers but are acceptable because UA is tech previewUX and OX bugs that would be GA blockers but are acceptable because UA is tech previewv23.1.5
Description
Describe the problem
The output of the above statement says that the system tenant doesn't have certain capabilities.
But it does!
Expected behavior
The output should be made to show the system tenant has these capabilities. The best way to achieve that is to ensure the system tenant has these capabilities in its tenant record to start with.
(We can either: modify the migration that creates the record to populate it; or, change the code that loads the record from the table to add the capabilities to it if they were not there to start with)
Jira issue: CRDB-25496
Epic CRDB-26691
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual teamua-ux-papercutUX and OX bugs that would be GA blockers but are acceptable because UA is tech previewUX and OX bugs that would be GA blockers but are acceptable because UA is tech previewv23.1.5