[ 
https://issues.apache.org/jira/browse/CASSANDRA-8349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Chu updated CASSANDRA-8349:
----------------------------------
    Description: 
Running cqlsh using Cassandra 2.1.2 on a single node.

Reproduction steps in cqlsh:

CREATE KEYSPACE a WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': 1};
CREATE TABLE a.a (a INT PRIMARY KEY);

INSERT INTO a.a (a) VALUES (1);
SELECT * FROM a.a;

ALTER KEYSPACE a WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': 2};

SELECT * FROM a.a;
DESCRIBE KEYSPACE a

Errors:
Column family 'a' not found

Workaround:
Restart cqlsh

  was:
Running cqlsh using Cassandra 2.1.2 on a single node.

Reproduction steps in cqlsh:

CREATE KEYSPACE a WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': 1};
CREATE TABLE a.a (a INT PRIMARY KEY);
INSERT INTO a.a (a) VALUES (1);
SELECT * FROM a.a;
ALTER KEYSPACE a WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': 2};
SELECT * FROM a.a;
DESCRIBE KEYSPACE a

Errors:
Column family 'a' not found

Workaround:
Restart cqlsh


> Using cqlsh to alter keyspaces causes tables not to be found
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-8349
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8349
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joseph Chu
>            Priority: Minor
>
> Running cqlsh using Cassandra 2.1.2 on a single node.
> Reproduction steps in cqlsh:
> CREATE KEYSPACE a WITH replication = {'class': 'SimpleStrategy', 
> 'replication_factor': 1};
> CREATE TABLE a.a (a INT PRIMARY KEY);
> INSERT INTO a.a (a) VALUES (1);
> SELECT * FROM a.a;
> ALTER KEYSPACE a WITH replication = {'class': 'SimpleStrategy', 
> 'replication_factor': 2};
> SELECT * FROM a.a;
> DESCRIBE KEYSPACE a
> Errors:
> Column family 'a' not found
> Workaround:
> Restart cqlsh



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

Reply via email to