Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 16 Jun 2015 21:49:00 +0000 (UTC)
From: "Sebastian Estevez (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12838309.1434491298000.89694.1434491340323@Atlassian.JIRA>
In-Reply-To: <JIRA.12838309.1434491298000@Atlassian.JIRA>
References: <JIRA.12838309.1434491298000@Atlassian.JIRA>
 <JIRA.12838309.1434491298648@arcas>
Subject: [jira] [Created] (CASSANDRA-9605) Error message when creating a KS
 replicated to a non-existent DC
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sebastian Estevez created CASSANDRA-9605:
--------------------------------------------

             Summary: Error message when creating a KS replicated to a non-existent DC
                 Key: CASSANDRA-9605
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9605
             Project: Cassandra
          Issue Type: Bug
            Reporter: Sebastian Estevez
            Priority: Minor


One of the most common mistakes I see with beginners is they mix up the data center configuration when using network topology strategy because they are copying from some tutorial or sample code or have recently changed snitches.

This should not be legal:
{code}
create KEYSPACE  test1 WITH replication = {'class': 'NetworkTopologyStrategy', 'doesnotexist': 1} ;
cqlsh> desc KEYSPACE test1 ;

CREATE KEYSPACE test1 WITH replication = {'class': 'NetworkTopologyStrategy', 'doesnotexist': '1'}  AND durable_writes = true; 
{code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)