[ https://issues.apache.org/jira/browse/CASSANDRA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1607: -------------------------------------- Component/s: API Summary: Remove ConsistencyLevel.ZERO (was: Deprecate ConsistencyLevel.ZERO) > Remove ConsistencyLevel.ZERO > ---------------------------- > > Key: CASSANDRA-1607 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1607 > Project: Cassandra > Issue Type: Improvement > Components: API > Affects Versions: 0.3 > Reporter: Brandon Williams > Assignee: Brandon Williams > Fix For: 0.7.0 > > > I've never heard of a valid use case for CL.ZERO, but I've seen countless > people run OOM from using it. Each time, I tell them to use ONE instead and > they do, clearly because they don't know why they chose ZERO to begin with. > If someone does figure out a use case for this in the future, they can > describe_ring, hash the key themselves to find the correct node, and use > CL.ONE with the commit log in periodic mode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.