[
https://issues.apache.org/jira/browse/CASSANDRA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105038#comment-13105038
]
Todd Nine commented on CASSANDRA-3209:
--------------------------------------
Unfortunately this was on a testing cluster which has since been shut down, so
I don't have the system.log output.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
