[
https://issues.apache.org/jira/browse/CASSANDRA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127160#comment-13127160
]
Pavel Yaskevich commented on CASSANDRA-3209:
--------------------------------------------
I can confirm that this is not a problem for latest 0.8/1.0/trunk branch
{noformat}
[default@unknown] describe cluster;
Cluster Information:
Snitch: org.apache.cassandra.locator.SimpleSnitch
Partitioner: org.apache.cassandra.dht.RandomPartitioner
Schema versions:
22b661a0-f5f7-11e0-0000-fe8ebeead9da: [127.0.0.1]
4b324db0-f5f7-11e0-0000-7fd66bb03aeb: [127.0.0.2, 127.0.0.3]
[default@unknown] create keyspace ks3;
SchemaDisagreementException()
[default@unknown]
{noformat}
cassandra-1.0.0 branch still have
{noformat}
catch (InvalidRequestException e)
{
throw new RuntimeException(e.getWhy());
}
catch (Exception e)
{
throw new RuntimeException(e.getMessage(), e);
}
{noformat}
in executeAddKeySpace method which could lead to NullPointerException if the
message wasn't set. Can we still fix this for 1.0.0 or is it freezed completely?
> 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.
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
