sql: investigate whether session revival should be made available to UA clusters #116537
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Describe the problem
We currently gate session revival both on a non-public cluster setting and on whether we are in a secondary tenant. UA clusters will always be running in secondary tenant, making this secondary check less effective.
This seems relatively minor to me since the tenant setting itself is SystemVisible, so users would have to go out of their way to enable this non-public setting.
Jira issue: CRDB-34662
The text was updated successfully, but these errors were encountered: