cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3981) Don't include original exception class name in CQL message
Date Wed, 29 Feb 2012 16:35:56 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne updated CASSANDRA-3981:
----------------------------------------

    Attachment: 3981.patch

Attaching trivial but actually only against CQL3. It does affect CQL2 too, but in a way, changing
the error message could break clients code (if they weren't very careful) so I figured, why
not leaving it the way it is for CQL2.
                
> 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

        

Mime
View raw message