Skip to content
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

Support KeySpace #359

Open
3 tasks
iosmanthus opened this issue Jul 15, 2022 · 0 comments
Open
3 tasks

Support KeySpace #359

iosmanthus opened this issue Jul 15, 2022 · 0 comments
Assignees

Comments

@iosmanthus
Copy link
Member

KeySpace is fundamental for transaction safety and multi-tenant features for TiKV. This is the tracking issue for the feature in client-rust. For tracking issues of other components, check:

Currently, #353 has introduced a new type parameter for both the transaction and the raw client to support an extensible request codec. We have two implementations for now: plain API V1 and API V2 with the keyspace feature. However, we only support constructing a new API V2 instance by ApiV2::default(). More new functions should be provided to enable users to create keyspaces by keyspace_name or keyspace_id. This requires:

  • implement acquiring keyspace info from PD. @iosmanthus
  • introduces a keyspace cache for each instance of the client. @iosmanthus
  • unit/integration tests for API v2 @iosmanthus
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant