You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2015/06/10 15:56:00 UTC

[jira] [Commented] (CASSANDRA-9247) DROP INDEX ks.index_name is a syntax error in 2.0

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

Benjamin Lerer commented on CASSANDRA-9247:
-------------------------------------------

The patch cause the following problem:

{code}
cqlsh:test> create table myTable (a int primary key, b int, c int);
cqlsh:test> create index WithCapitalLetters ON myTable (b);
cqlsh:test> drop index WithCapitalLetters;
Bad Request: Index 'withcapitalletters' could not be found in any of the column families of keyspace 'test'
cqlsh:test>
{code} 

We had a similar issue in 2.1. Your patch should make sure that {{CREATE INDEX}} handle the index name in the same way as the {{DROP INDEX}}. 

> DROP INDEX ks.index_name is a syntax error in 2.0
> -------------------------------------------------
>
>                 Key: CASSANDRA-9247
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9247
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Carl Yeksigian
>            Priority: Minor
>             Fix For: 2.0.x
>
>
> In all versions of 2.0, statements like
> {{DROP INDEX ks.index_to_drop;}}
> fail with the error
> {{ErrorMessage code=2000 [Syntax error in CQL query] message="line 1:13 missing EOF at '.'"}}
> The error doesn't happen in any 2.1 versions or trunk. [The docs|http://docs.datastax.com/en/cql/3.1/cql/cql_reference/drop_index_r.html] don't indicate that the {{DROP INDEX}} statement should work any differently on 2.0.
> [Here|https://github.com/mambocab/cassandra-dtest/blob/drop_index_keyspace_bug/index_keyspace_bug.py] is a dtest that produces the error, but I think a patch should include a more isolated test for the component that's failing here.



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