cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Chu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8349) ALTER KEYSPACE causes tables not to be found
Date Fri, 21 Nov 2014 17:55:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221171#comment-14221171
] 

Joseph Chu commented on CASSANDRA-8349:
---------------------------------------

Yes just restarting cqlsh works as well. I've also tried out DevCenter, which does not show
this issue. It seems to be specific only to cqlsh in 2.1.2. I'll edit the description to reflect
the changes.

> ALTER KEYSPACE 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 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 the instance



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

Mime
View raw message