cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2570) CQL: incorrect error message running truncate on CF that does not exist
Date Wed, 27 Apr 2011 10:48:03 GMT

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

Pavel Yaskevich updated CASSANDRA-2570:
---------------------------------------

    Attachment: CASSANDRA-2570.patch

Working branch: trunk. QP now checks if the given CF exists in the current KS before executing
"truncate" operation.

> CQL: incorrect error message running truncate on CF that does not exist
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-2570
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2570
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.8 beta 1
>            Reporter: Cathy Daw
>            Assignee: Pavel Yaskevich
>            Priority: Trivial
>              Labels: cql
>             Fix For: 0.8.0
>
>         Attachments: CASSANDRA-2570.patch
>
>
> Run truncate on a CF that does not exist. The error message is misleading.
> *CQLSH*
> {code}
> cqlsh> truncate aaaa;
> Unable to complete request: one or more nodes were unavailable.
> {code}
> *cassandra-cli*
> {code}
> [default@cqldb] truncate aaaaaaaaa;
> aaaaaaaaa not found in current keyspace.
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message