Skip to content
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

Configurable Cassandra consistency level #1026

Merged
merged 1 commit into from
Feb 26, 2016

Conversation

subnetmarco
Copy link
Member

Closes #1013.

@subnetmarco subnetmarco self-assigned this Feb 26, 2016
@subnetmarco subnetmarco force-pushed the feature/cassandra-consistency branch 2 times, most recently from aac5204 to d2268a0 Compare February 26, 2016 03:55
@subnetmarco
Copy link
Member Author

@thibaultcha can you review this?

@@ -23,6 +23,7 @@ describe("Cassadra factory", function()
contact_points = dao_properties.contact_points,
keyspace = dao_properties.keyspace,
query_options = {
consistency = 1,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should use the value from the cassandra.consistencies enum and not the underlying value

@subnetmarco
Copy link
Member Author

I have updated the PR. If it looks good I will squash and merge.

@thibaultcha
Copy link
Member

Ok. Those tests don't exist in feature/postgres anyways

On Feb 25, 2016, at 10:18 PM, Marco Palladino [email protected] wrote:

I have updated the PR. If it looks good I will squash and merge.


Reply to this email directly or view it on GitHub.

@subnetmarco subnetmarco added pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release) and removed pr/status/needs review labels Feb 26, 2016
subnetmarco added a commit that referenced this pull request Feb 26, 2016
Configurable Cassandra consistency level
@subnetmarco subnetmarco merged commit ee87ecb into next Feb 26, 2016
@subnetmarco subnetmarco deleted the feature/cassandra-consistency branch February 26, 2016 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants