refactor: introduce UninitTenant
and TIdentRaw
#15207
Merged
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.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
refactor: introduce
UninitTenant
andTIdentRaw
Tenant
is a meta-service key component representing a tenant,with a embedded per-tenant config.
UninitTenant
is a shadow ofTIdent
but without config thus it cannot be used as a key.
UninitTenant
can be initialized to build aTenant
for use as ameta-service key.
Correspondingly, this commit introduce
TIdentRaw
as an uninitializedversion of
TIdent
.TIdentRaw
does not cantain per-tenant config and is only used insidemeta-service values(not keys), which could be
serde
.Other changes:
Populate usage of
Tennat
toCatalog
implementation.Tests
Type of change
Related Issues
This change is