cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10658) Some DROP ... IF EXISTS incorrectly result in exceptions on non-existing KS
Date Fri, 27 Nov 2015 09:13:11 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029649#comment-15029649
] 

Robert Stupp commented on CASSANDRA-10658:
------------------------------------------

bq. could you add tests for these as well?

The ConfigurationException was thrown from {{CQL3Type.Raw#prepare(java.lang.String)}} via
{{DropFunction/AggregateStatement.prepare}}.
There are tests in UFTest and AggregationTest (testNonExistingOnes) that check for the correct
message.
I've changed the test code to check for the exception class as well (pushed to the 3.0 and
trunk branches).

> Some DROP ... IF EXISTS incorrectly result in exceptions on non-existing KS
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10658
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10658
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>            Priority: Minor
>             Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> 2.1, 2.2 and 3.0 incorrectly throws {{InvalidRequestException}} on non-existing keyspace
for {{DROP TYPE IF EXISTS}}
> 3.0 incorrectly throws {{ConfigurationException}} for {{DROP AGGREGATE IF EXISTS}} with
type arguments.
> 3.0 incorrectly throws {{ConfigurationException}} for {{DROP FUNCTION IF EXISTS}} with
type arguments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message