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
Request to add TransactionDB and OptimisticTransactionDB to rockdbjni #1151
Comments
Hi @Kangmo I am already working on this and hope to have something in the next week or two. |
Thanks Adam, that is great news! 2016년 6월 4일 토요일, Adam Retternotifications@github.com님이 작성한 메시지:
|
Hi Adam, is there a branch that I can test the two classes before the release? It would be great if there is any to try out these classes. Thanks for providing two classes in advance. |
Hi @adamretter, any progress on this feature? Would love to test it out on a project I am working on. Thanks very much. |
Hi @adamretter, I also would love to test it out, and waiting for this feature to keep RocksDB data consistent in my project, ScaleChain. |
I am working on it. It's just taking a while I am afraid. The WIP is visible here https://github.com/adamretter/rocksdb/tree/java-transactions |
Hi @adamretter, thanks for the update. I have some questions on the transaction feature. Example> Does transaction B wait for the lock on key1 held by Transaction A? |
Duplicate of #697 |
@Kangmo You are best to look at the Transaction Samples: https://github.com/adamretter/rocksdb/tree/java-transactions/java/samples/src/main/java |
Closing this via automation due to lack of activity. If discussion is still needed here, please re-open or create a new/updated issue. |
Hi,
I am assuming that these two classes are missing in rocksdbjni.
It would be great if I can achieve atomicity of my transaction using either TransactionDB or OptimisticTransactionDB.
I request to add these two classes to rocksdbjni.
It would be great if you have any planned release day for the new rocksdbjni with these (or one of these) classes.
RocksDB rocks!!
The text was updated successfully, but these errors were encountered: