-
Notifications
You must be signed in to change notification settings - Fork 320
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
[DISCUSS]Whether the creation of cluster_schema database is allowed in the new tenant #1567
Comments
lutengda
added a commit
to lutengda/cnosdb
that referenced
this issue
Jan 10, 2024
4 tasks
roseboy-liu
pushed a commit
that referenced
this issue
Jan 10, 2024
version: cnosdb 2.4.0, revision db434d4 |
@roseboy-liu The PR fix this issue need sync LTS/2.3. |
lutengda
added a commit
to lutengda/cnosdb
that referenced
this issue
Jan 23, 2024
fix: 'cnosdb' and other tenant check system db(cnosdb#1567)
4 tasks
roseboy-liu
pushed a commit
that referenced
this issue
Jan 23, 2024
fix: 'cnosdb' and other tenant check system db(#1567)
version: cnosdb 2.3.4, revision 07e229d |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Whether the creation of cluster_schema database is allowed in the new tenant.The current situation is that when creating a cluster_schema database in a new tenant, an error is reported: cluster_schema already exists.In fact, we only created the cluster_schema database under the cnosdb database. It does not exist under the new tenant.When we switch to the cluster_schema database and create a table, another error will be reported: cluster_schema not found.This situation is inconsistent, and I hope there can be a better way to handle it.
![image](https://private-user-images.githubusercontent.com/40594937/273573706-67879629-532c-4c0d-a384-e1596421d838.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI1MjQzMTUsIm5iZiI6MTcyMjUyNDAxNSwicGF0aCI6Ii80MDU5NDkzNy8yNzM1NzM3MDYtNjc4Nzk2MjktNTMyYy00YzBkLWEzODQtZTE1OTY0MjFkODM4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODAxVDE0NTMzNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM5YWZjNmVhZTg2ZWYwMzdkMDk4MDc3YTVlNjc4MzQwZGRjYThmYTMyNGM0ZjFhNjUwZGViNTdhYTUwYTkxY2YmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.BaEfCH6C3P8HpYcHhSF8Qsv4U3U16YON2tNJa2nRoPE)
To Reproduce
No response
Expected behavior
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: