Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 5 Jan 2013 00:56:13 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12609851.1349141273830.84393.1357347373017@arcas>
In-Reply-To: <JIRA.12609851.1349141273830@arcas>
References: <JIRA.12609851.1349141273830@arcas>
Subject: [jira] [Commented] (CASSANDRA-4745)  Required field 'keyspace' was
 not present! when modifying a keyspace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-4745:
----------------------------------------------

1.1.4 is indeed affected, however, and so is 1.1.5, but this is no longer an issue since 1.1.6 (don't know the exact issue).
                
>  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
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 1.2.1
>
>
> 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