-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
store: make it easier to implement new storage engines for TiDB #782
Comments
sounds great, will keep watching your progress, 👍 |
This was referenced Dec 24, 2015
xhebox
pushed a commit
to xhebox/tidb
that referenced
this issue
Sep 28, 2021
xhebox
pushed a commit
to xhebox/tidb
that referenced
this issue
Oct 8, 2021
ti-chi-bot
pushed a commit
that referenced
this issue
Oct 9, 2021
rleungx
pushed a commit
to rleungx/tidb
that referenced
this issue
Feb 26, 2024
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io> Co-authored-by: cfzjywxk <lsswxrxr@163.com> Co-authored-by: ShuNing <nolouch@gmail.com> fix pingcap#35418 (pingcap#47951) (pingcap#48101) close pingcap#35418 close tikv/pd#7509
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, interfaces in kv and store package are too complicated and disordered. It is very hard to implement a new storage engine for TiDB.
I plan to make it easier with following steps:
The text was updated successfully, but these errors were encountered: