-
Notifications
You must be signed in to change notification settings - Fork 326
Added consistency parameter to cassandra connection string #114
Conversation
Can we get this merged? |
Not sure who to bother, exactly. |
@mattes Can we get this PR merged? |
1 similar comment
@mattes Can we get this PR merged? |
I have merged this change in our fork if needed: https://github.com/gemnasium/migrate |
This no longer needs ParseConsistency(), this function has be put into master gocql ParseConsistencyWrapper() |
@mattes Can we get this PR merged? |
I was wondering about the status of this PR? I am running into the same issues. Thanks! |
Luke, use the fork
|
Hope @mattes takes a look at this repo at some point. Last commit was in On Wed, Sep 28, 2016 at 2:42 PM Philippe Lafoucrière <
|
Thanks for the PR. Merging. |
Migrate is great. I love it. That said, my development environment doesn't have a full, multi-node Cassandra setup - I have one single container. This makes the default consistency of the Cassandra driver (
gocql.All
) problematic. So, I added a way to specify consistency in the connection string - the same way protocol may be specified. For example,This PR is a continuation of #112 (moved branches).