[
https://issues.apache.org/jira/browse/CASSANDRA-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763057#comment-13763057
]
Sylvain Lebresne commented on CASSANDRA-5953:
---------------------------------------------
I don't know how much that matters, but as far as I can tell, we've never
validated such a thing (I'm able to reproduce the exact same with the cli on
1.2 at least).
Which leads me to the question: do we really want to refuse it? Feels to me
that handling non-existing nodes the same way than dead ones is rather sane.
And actually I think that refusing this could be a tad painful if someone wants
to up its RF.
> Replication validation is broken
> --------------------------------
>
> Key: CASSANDRA-5953
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5953
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.2.10
>
>
> On my local, single node cluster, RF=3 inserts should not succeed:
> {noformat}
> cqlsh> CREATE KEYSPACE mykeyspace WITH REPLICATION = { 'class' :
> 'SimpleStrategy', 'replication_factor' : 3 };
> cqlsh> use mykeyspace ;
> cqlsh:mykeyspace> CREATE TABLE users (
> ... user_id int PRIMARY KEY,
> ... fname text,
> ... lname text
> ... );
> cqlsh:mykeyspace> INSERT INTO users (user_id, fname, lname)
> ... VALUES (1745, 'john', 'smith');
> cqlsh:mykeyspace> select * from users;
> user_id | fname | lname
> ---------+-------+-------
> 1745 | john | smith
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
