-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Plans for SQL Layer? #198
Comments
It's possible to use TiDB as the SQL layer. The architecture of TiDB is highly leveled, the storage engine in TiDB is pluggable. Currently TiDB uses TiKV as a distributed storage engine and goleveldb as a local storage engine for testing. TiDB https://github.com/pingcap/tidb |
It'd be great to get community feedback on layer needs more generally, including SQL. I'd encourage you to kick off a discussion on the forums: https://forums.foundationdb.org. As we note in our Contributors Guide our hope is to make forums the place where most development and user discussion takes place, instead of GitHub issues. "GitHub Issues should be used for tracking tasks. If you know the specific code that needs to be changed, then it should go to GitHub Issues. Everything else should go to the Forums." Hope it's OK that I close this issue for now, in hopes of the discussion migrating to the forums. It'd also be good to circle back here with a link to wherever the discussion migrates. Thanks! |
There is a simple SQL layer on FoundationDB, https://github.com/opentradesolutions/opentick |
Actually, four year ago, there's already a sql layer for FDB: https://github.com/jaytaylor/sql-layer. |
What are the current plans for the SQL layer?
The text was updated successfully, but these errors were encountered: