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

store: make it easier to implement new storage engines for TiDB #782

Closed
disksing opened this issue Dec 23, 2015 · 1 comment
Closed

store: make it easier to implement new storage engines for TiDB #782

disksing opened this issue Dec 23, 2015 · 1 comment
Assignees

Comments

@disksing
Copy link
Contributor

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:

  1. Simplify local store and hbase store. Storages should implement as less interfaces as possible.
  2. Refine interfaces. Distinguish interfaces that should be completed by storages from those are already complete in kv.
  3. Write a guide document.
@nieyy
Copy link

nieyy commented Dec 23, 2015

sounds great, will keep watching your progress, 👍

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

3 participants