Define a Cassandra conistency level

Bug #1409782 reported by Christopher Powell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Poppy
Fix Released
Medium
Tony Tan

Bug Description

A consistency level needs to be explicitly defined in poppy. The default level according to the documentation is ONE, which could lead to data inconsistency. A default level of LOCAL_QUORUM is suggested.

http://datastax.github.io/python-driver/getting_started.html#setting-a-consistency-level-with-prepared-statements

Changed in poppy:
importance: Undecided → Medium
milestone: none → kilo-2
Changed in poppy:
assignee: nobody → Tony Tan (tonytan4ever)
Revision history for this message
Amit Gandhi (amit-gandhi) wrote :
Changed in poppy:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to poppy (master)

Reviewed: https://review.openstack.org/147326
Committed: https://git.openstack.org/cgit/stackforge/poppy/commit/?id=95a944763f2cb6cb1af483df7a3e3ef528a0601b
Submitter: Jenkins
Branch: master

commit 95a944763f2cb6cb1af483df7a3e3ef528a0601b
Author: tonytan4ever <email address hidden>
Date: Wed Jan 14 14:20:29 2015 -0500

    Add cassandra consistency level
    Closes-Bug: 1409782

    Change-Id: Ic53b2ac32592458bd4b32c6edfa51a04415fa1cf

Changed in poppy:
status: In Progress → Fix Committed
Changed in poppy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.