cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3209) CLI does not display error when it is not possible to create a keyspace when schemas in cluster do not agree.
Date Fri, 14 Oct 2011 02:08:12 GMT

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

Jonathan Ellis commented on CASSANDRA-3209:
-------------------------------------------

We can fix 1.0 branch -> 1.0.1 release.  1.0.0 release is frozen.
                
> CLI does not display error when it is not possible to create a keyspace when schemas
in cluster do not agree.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3209
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3209
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.1
>         Environment: Latest brisk beta 2 deb on Ubuntu 10.10 server 64 bit.  (Using chef
recipe to install)
>            Reporter: Todd Nine
>            Assignee: Pavel Yaskevich
>              Labels: cli
>             Fix For: 1.0.0
>
>         Attachments: CASSANDRA-3209.patch
>
>
> Cluster:
> 3 nodes.  2 online, 1 offline
> describe cluster; displays 2 schema versions.  2 nodes are on 1 version, a single node
is on a different version.
> Issue this command in the CLI.
> create keyspace TestKeyspace with placement_strategy = 'org.apache.cassandra.locator.NetworkTopologyStrategy'
and strategy_options=[{Brisk:3, Cassandra:0}];
> What should happen.
> An error should be displayed when the keyspace cannot be created.
> What actually happens.
> The user is presented with "null" as the output.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message