You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2010/10/12 00:43:33 UTC
[jira] Commented: (CASSANDRA-1607) Deprecate ConsistencyLevel.ZERO
[ https://issues.apache.org/jira/browse/CASSANDRA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920016#action_12920016 ]
Brandon Williams commented on CASSANDRA-1607:
---------------------------------------------
To clarify, I mean take CL.ZERO out back and shoot it in the head, not deprecate it. Remove it completely.
> Deprecate ConsistencyLevel.ZERO
> -------------------------------
>
> Key: CASSANDRA-1607
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1607
> Project: Cassandra
> Issue Type: Improvement
> 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.