-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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.
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
externalconn/testutils: fix a mistake in SetSQLDBForUser #110005
Conversation
Release note: None
Before this patch, the DefaultZoneConfig field was taken from the global default. This is incorrect. This patch fixes it. Note that this patch is not complete - we also need to update the non-test version of tenant configs, by communicating the default config from the KV layer to the SQL service over the network (using tenant connector). Release note: None
Release note: None
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sometimes for fixes like this I think it is useful to describe why/how this was working before.
We might want to take a second look at spanconfigtestcluster
since I think this code was copied from there.
Prior to this patch, this method was incorrectly swapping a SQL connection to the secondary tenant for one to the system tenant. This patch fixes it. Note: the problem was "invisible" because this incorrect redirect was the first thing that ever happened in any data file to a secondary tenant. So really all the "multi-tenant" testdata files were really exercising the system tenant. Release note: None
Done. (added to commit message)
Done - it's unaffected because it does not contain a SetSQLDBForUser method. |
e16128a
to
547a048
Compare
TFYR! bors r=stevendanna |
Build succeeded: |
All commits but the last are from #110004 (review only the last commit here)
Prior to this patch, this method was incorrectly swapping a SQL
connection to the secondary tenant for one to the system tenant.
This patch fixes it.
Epic: CRDB-18499