-
Notifications
You must be signed in to change notification settings - Fork 21
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
Clarifications to datacake-sqlite readme #39
Comments
Hello! I'm sorry for not getting back to you sooner. Yes, the readme probably could do with being improved and a bit more explicit:
|
Are there any plans of having full SQL capability? What is the current limitation of having full SQLite capabilities being compatible with Datacake's eventual consistency? |
One would need to replace SQLIte's underlying KV store with a wrapper in order to correctly reflect changes. The reason for this is executing a SQL statement can create changes on multiple rows, and do not work well when you have multiple statements being executed and need to apply those changes in the correct order. The eventual consistency nature of datacake makes applying the statements in the right order is nearly impossible. |
Once RAFT consensus is implemented, do you think it'll be easier? |
Something like RAFT would indeed make it easier to do, it wouldn't be the same as the eventually consistent store, but that would be a good thing. Currently the biggest blocker for any sort of raft support is the eco system still feels a bit unstable / unimplemented currently. |
I'm approaching this project as a newcomer and have a couple of questions about the datacake-sqlite integration.
Thank you!
The text was updated successfully, but these errors were encountered: