comsat-mongodb-allanbanks #13
Conversation
…ntation of FiberMongoDatabaseImpl wrapper, skeleton of FiberMongoCollectionImpl wrapper
…dables; build now completes successfully
* Renamed project "comsat-mongodb" -> "comsat-mongodb-allanbanks" in order to stress the underlying implementation (with dual-licence policy) * Converted from partial wrapping approach to implementation subclassing and overriding approach. Previous blocking methods exported by the original implementation are fiber-blocking in this subclassing implementation. Interface compatibility is retained, so drop-in replacement becomes possible. Disadvantage is that this implementation now depends on non-API (implementation) from the allanbanks driver * Test classes structure in place together with first tests
MAJOR: upgraded to AllanBanks driver version 2.0, with more favorable licensing scheme as well
|
Wow !! |
|
The following error appears during the tests: The drop method itself is marked as suspendable, but runCommand is not, So the instrumentor doesn't find a reason to instrument it. In order to solve that, the following method has to be added to META-INF/suspendables: |
|
I'm not sure why I'm not getting the error when running fork's tests... I seem to have "verifyInstrumentation" enabled and I can see that the "scanSuspendables" task is correctly listing "com.allanbank.mongodb.client.MongoDatabaseImpl.runCommand" in "META-INF/suspendable-supers". Have you got it there? |
|
I am also running in your fork. |
…spendables list as per test warnings and eitan101's suggestion
|
Thanks! I've found the warning and added the new suspendable method, then the warning has disappeared |
|
Hi! I added some additional asserts for the future-based API in order to make sure the addListener+callback functionality works ok. Still clean merge and the stderr and stdout are still clean apart from some CPU hogging warnings coming from blocking calls in the tests (and ultimately driver's connection) setup stages. |
comsat-mongodb-allanbanks Thanks again!
Hi!
I implemented a mongodb integration module for comsat based on http://www.allanbank.com/mongodb-async-driver/index.html version 2.0 and a fairly complete essential testsuite for it based on Embed MongoDB https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo ; I think you might be interested in main comsat inclusion.
The module takes a subclassing approach, so existing code based on the driver should require minimal to no code changes. The overridden methods from the original driver are just the blocking and future ones in order to make them fiber-blocking. The fiber-blocking overrides are implemented by bridging the async, callback-based corresponding methods in the original driver through Quasar's FiberAsync.
I can think of further TODOs both for driver and tests but I think inclusion could be possible already (the 99 JUnit tests covering the overridden methods run all ok here); you can find those ideas in the classes' JavaDocs comments, but shortly:
Incidentally (and luckily), starting with version 2.0, the license for the basic driver functionality has changed to Apache 2.0 http://www.allanbank.com/mongodb-async-driver/license.html which, to the extent of my knowledge, allows for liberal use even in commercial projects (previously commercial use required a commercial licence, which I think was a more strict policy than comsat's). Maybe the author decided such a change because of 10gen's OSS driver starting to consider/implement an async interface in the 3.0.x branch https://github.com/mongodb/mongo-java-driver/tree/3.0.x/async-driver