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.

Sign up for GitHub

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

Jump to bottom

implement keyspace management #5293

Closed
11 tasks done
AmoebaProtozoa opened this issue Jul 11, 2022 · 1 comment
Closed
11 tasks done

implement keyspace management #5293

AmoebaProtozoa opened this issue Jul 11, 2022 · 1 comment
Labels
type/development The issue belongs to a development tasks

Comments

@AmoebaProtozoa
Copy link
Contributor

AmoebaProtozoa commented Jul 11, 2022 •
edited by rleungx
Loading

Development Task

In order to let multiple keyspaces share the same PD cluster, PD needs to provide storage and ways to manage keyspace metadata.

Feature request: tikv/tikv#12998
Parent Issue: tikv/tikv#12999

Task List
@AmoebaProtozoa AmoebaProtozoa added the type/development The issue belongs to a development tasks label Jul 11, 2022
This was referenced Jul 11, 2022
Merged
Merged
Merged
Merged
@ystaticy ystaticy mentioned this issue Jul 12, 2022
Open
13 tasks
This was referenced Jul 14, 2022
Closed
Open
This was referenced Jul 27, 2022
Merged
Merged
ti-chi-bot pushed a commit that referenced this issue Aug 8, 2022
@AmoebaProtozoa
storage: keyspace management (#5265)
e089172 
ref #5293

storage: keyspace management

Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>
ti-chi-bot added a commit that referenced this issue Aug 22, 2022
@AmoebaProtozoa @ti-chi-bot
server: keyspace management (#5291)
b388217 
ref #5293

storage: keyspace management

Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>

Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot added a commit that referenced this issue Aug 30, 2022
@AmoebaProtozoa @nolouch @ti-chi-bot
client: keyspace client (#5297)
1efd822 
ref #5293

client: keyspace management gRPC client

Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>

Co-authored-by: ShuNing <nolouch@gmail.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
@CabinfeverB CabinfeverB mentioned this issue Oct 11, 2022
Merged
This was referenced Jan 10, 2023
Merged
Merged
ti-chi-bot added a commit that referenced this issue Jan 10, 2023
@AmoebaProtozoa @ti-chi-bot
kv: added RunInTransaction style transaction interface (#5347)
1b778f2 
ref #5293

Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>

Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
@JmPotato JmPotato mentioned this issue Jan 13, 2023
Merged
ti-chi-bot pushed a commit that referenced this issue Jan 13, 2023
@JmPotato
storage: unify the keyspace naming (#5863)
0f75293 
ref #5293

Unify the keyspace naming.

Signed-off-by: JmPotato <ghzpotato@gmail.com>
@AmoebaProtozoa AmoebaProtozoa mentioned this issue Jan 16, 2023
Merged
ti-chi-bot pushed a commit that referenced this issue Jan 17, 2023
@AmoebaProtozoa
keyspace: Pre alloc keyspace (#5869)
7ea589e 
ref #5293

Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>
ti-chi-bot added a commit that referenced this issue Feb 2, 2023
@AmoebaProtozoa @ti-chi-bot
apiv2: keyspace management (#5313)
abb62d2 
ref #5265, ref #5291, ref #5293, ref #5297

Add APIv2 HTTP interface for keyspace management.

Signed-off-by: David <8039876+AmoebaProtozoa@users.noreply.github.com>

Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
@rleungx
Copy link
Member

rleungx commented Jul 26, 2023 •
edited
Loading

Close it since it has been finished.

@rleungx rleungx closed this as completed Jul 26, 2023
@ystaticy ystaticy mentioned this issue Dec 6, 2023
Open
20 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/development The issue belongs to a development tasks
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AmoebaProtozoa @rleungx