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

Robert Stupp edited comment on CASSANDRA-7590 at 7/24/14 6:57 AM:
------------------------------------------------------------------

But for example {{DROP TABLE IF EXISTS}} with non-existing KS does not complain.
{noformat}
cqlsh> drop table fool.nonex;
code=2200 [Invalid query] message="Keyspace fool does not exist"
cqlsh> drop table if exists fool.nonex;
cqlsh> 
{noformat}

The patches are 7590-drop-index-npe-assert.txt (ignores non-existing KS) and
7590-drop-index-npe-assert-ks.txt (ignore non-existing KS).



was (Author: snazy):
But for example {{DROP TABLE IF EXISTS}} with non-existing KS does not complain.
{noformat}
cqlsh> drop table fool.nonex;
code=2200 [Invalid query] message="Keyspace fool does not exist"
cqlsh> drop table if exists fool.nonex;
cqlsh> 
{noformat}

The patches are 7590-drop-index-npe-assert.txt ignoring non-existing KS.
The patches are 7590-drop-index-npe-assert-ks.txt not ignoring non-existing KS.


> java.lang.AssertionError when using DROP INDEX IF EXISTS on non-existing index
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7590
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7590
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Hanh Dang
>            Assignee: Robert Stupp
>            Priority: Minor
>              Labels: cql
>             Fix For: 2.1.0
>
>         Attachments: 7590-drop-index-npe-assert-ks.txt, 
> 7590-drop-index-npe-assert.txt
>
>
> To reproduce: 
> cqlsh> CREATE KEYSPACE test WITH REPLICATION = {'class':'SimpleStrategy', 
> 'replication_factor':1};
> cqlsh> USE test;
> cqlsh:test> DROP INDEX IF EXISTS fake_index;
> <ErrorMessage code=0000 [Server error] message="java.lang.AssertionError">



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to