-
Notifications
You must be signed in to change notification settings - Fork 750
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
New meta API #5012
Comments
In the current impl, creating a database involves updating two keyspaces: This will make renaming a DB easy and troubleless. We're still using the two-keyspace design? |
As #4918 discussed, with this issue's create table operation, there are some self defined function like get_database_id, how can we use it in the meta transaction api? |
To batch-delete tables, without the need to understand business for The kv namespaces would look like:
And the operations would be done by constraining the versions of resources it depends on. Every txn is done by several Create db:
Delete db and all its tables:
Create table:
|
👍 Good to me. |
To better meet the needs, welcome to describe the pseudo-code operation for the new meta api:
|
I have some questions. take
|
These two are similar: the reading part can be done on either the client-side or server-side.
I am not quite sure about this. But I thought a database probably relies on
To write a value that is not a const value, it needs some other syntax to be well defined. But it's totally feasible, IMHO. |
In my mind, Alter database db_name rename to new_db_name; like this:
|
@TCeason
typo: db_meta -> db_id
IMHO, renaming a database does not need to update the version of |
|
Use some short-circuit in
|
@youngsofun |
I was wondering about that too. the setting is: key1 and key2 are all ways created/deleted at the same time.
|
I do not know. It is up to the application and has to enumerate every possible write operation on them.
It will be a severe bug IMHO. The best way is to stop doing anything :) |
maybe this
the db_id also may be acquired by other at the same time. may be move this alloc db id action in Txn?
|
A seq number generated by metasrv will never be reused. This is safe. |
Most of the implementation tasks are done, except for some refactoring and testing jobs. Is it time to close this issue since the design of txn-based schema-API is nailed now? |
Summary
Consider moving the meta API to KV api, we have the follows operations:
@drmingdrmer @lichuang Help to see if there is something wrong with these logic above? And would like to know what is the underlying logic of current meta API.
The text was updated successfully, but these errors were encountered: