cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Coverston (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-4745) Required field 'keyspace' was not present! when modifying a keyspace
Date Tue, 02 Oct 2012 01:29:07 GMT
Benjamin Coverston created CASSANDRA-4745:
---------------------------------------------

             Summary:  Required field 'keyspace' was not present! when modifying a keyspace
                 Key: CASSANDRA-4745
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4745
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.1.4
            Reporter: Benjamin Coverston


cassandra-cli gets stuck after updating an existing keyspace.

To reproduce, create the KS/CF through cassandra-stress then update the keyspace as shown
below in the CLI.


notroot@datastax-training:~/cassandra$ bin/cassandra-cli 
Connected to: "Test Cluster" on 127.0.0.1/9160
Welcome to Cassandra CLI version 1.1.4

Type 'help;' or '?' for help.
Type 'quit;' or 'exit;' to quit.

[default@unknown] update keyspace Keyspace1                     
...	with placement_strategy = 'SimpleStrategy'    
...	and strategy_options = {replication_factor:2};
Not authenticated to a working keyspace.
fa270c1d-7c85-3dfc-98b0-db0755f853f3
Waiting for schema agreement...
... schemas agree across the cluster
org.apache.thrift.protocol.TProtocolException: Required field 'keyspace' was not present!
Struct: describe_keyspace_args(keyspace:null)
[default@unknown] 
[default@unknown] use Keyspace1;
Login failure. Did you specify 'keyspace', 'username' and 'password'?


--
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

Mime
View raw message