Async mongodb driver#180
Conversation
|
Note says that the Travis Build Failed but it appears to be an issue with Travis not being able to download artifacts from Maven. Can someone trigger a manual rebuild? |
|
@allanbank I bumped if for a rebuild (even though the Github status does not show the reubuild). |
|
I restarted the build now that the mapkeeper stuff is out of the way. I'd like to get this set of changes merged in before cutting the next release. If someone from the mongo community can work with me on needed updates, I'll proactively go point the related open issues here and close them. |
There was a problem hiding this comment.
the java home stuff is good, but seems unrelated to the rest of the mongo improvements. If I file an issue for "allow the use of java home" could you edit the commit message to call out closing it?
There was a problem hiding this comment.
great. presuming you go forward with the rebase, please edit the commit message for this part of the changes to note "fixes #252"
|
@busbey - Give me a day or two to make the changes you suggested. Is it OK if I rebase the pull on the latest master making the changes as I go? |
|
please feel free to rebase. I prefer rebases to lots of merges, personally. :) |
Allow setting the java version to use via the "JAVA_HOME" environment variable. Fixes brianfrankcooper#252.
…level will throw exceptions and be caught in catch block
Changed reference to original forked repo which is not maintained to this repo to avoid conflicting instructions. Might want to do that for top level README as well.
When running workloads that use the "insert" operation, we get a lot of duplicate key exceptions from the server. Changing to upsert to avoid these exceptions.
URI to configure the client. Old properties are deprecated and but will be added to the URI if present and the URI does not already contain a value for the setting.
to the 3.0 driver from MongoDB Inc. and updated to the new Document and fluent APIs.
a243b47 to
6970ee1
Compare
|
@busbey - I think that latest push covers all of the issues you raised. Let me know if I missed something. Rob. |
|
The update looks great. It looks like with the current update we'll be using the Mongo 3 client, right? Will that prevent us from talking to Mongo 2 servers? If so, how comon are Mongo 2 installations? Is it worth maintaining both, ala our HBase binding? |
|
The driver can talk to version 2 and 3 clusters. Rob On May 23, 2015 12:22:12 PM EDT, Sean Busbey notifications@github.com wrote:
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
[Mongodb] merge adds Async mongodb driver, update normal driver to talk to mongo 2 and 3 clusters.
|
Thanks for sticking with this contribution! I hope to see more great stuff from the mongo community in the future. |
|
@busbey - No problem. Thanks for doing the merge. I mentioned it in the initial pull request but I am pretty certain these pull requests can be closed now.
If you would like me to add an explicit comment to each of those explaining why it can be closed I'll be happy to do that. Rob. |
|
Thanks for the reminder, I'll go close them out. |
…driver [Mongodb] merge adds Async mongodb driver, update normal driver to talk to mongo 2 and 3 clusters.
…driver [Mongodb] merge adds Async mongodb driver, update normal driver to talk to mongo 2 and 3 clusters.
This pull request contains a new driver for MongoDB based on the asynchronous driver. The bulk of the changes are adding the required logic to the startup scripts to support the second driver. I have used this branch to run a series of benchmarks.
There are also a number of community contributed updates to the old MongoDB Driver. These include:
This pull request will supersede the following pull requests:
I know this is a large volume of changes but they are all focused on the MongoDB driver and thought it would be easier to provide them in one batch than a bunch of pull requests. If you would prefer a bunch of smaller changes I will need guidance on the desired granularity.