You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org> on 2012/02/29 23:59:57 UTC
[jira] [Commented] (CASSANDRA-3981) Don't include original
exception class name in CQL message
[ https://issues.apache.org/jira/browse/CASSANDRA-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219633#comment-13219633 ]
Jonathan Ellis commented on CASSANDRA-3981:
-------------------------------------------
+1
> Don't include original exception class name in CQL message
> ----------------------------------------------------------
>
> Key: CASSANDRA-3981
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3981
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Labels: cql
> Fix For: 1.1.0
>
> Attachments: 3981.patch
>
>
> In CreateColumnFamilyStatement, we do
> {noformat}
> catch (ConfigurationException e)
> {
> throw new InvalidRequestException(e.toString());
> }
> {noformat}
> This result in having the exception message looking like:
> {noformat}
> java.sql.SQLSyntaxErrorException: org.apache.cassandra.config.ConfigurationException: Cf1 already exists in keyspace Keyspace1
> {noformat}
--
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