You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "BAONING WU (JIRA)" <ji...@apache.org> on 2011/06/01 19:13:47 UTC

[jira] [Created] (CASSANDRA-2730) exception generate when using same index names

exception generate when using same index names
----------------------------------------------

                 Key: CASSANDRA-2730
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.8 beta 1
            Reporter: BAONING WU


when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
cqlsh> create index name_key on Tuser(name);
cqlsh> create index name_key on Tuser(state);
note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.


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

[jira] [Issue Comment Edited] (CASSANDRA-2730) exception generate when using same index names

Posted by "Cathy Daw (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042349#comment-13042349 ] 

Cathy Daw edited comment on CASSANDRA-2730 at 6/1/11 6:30 PM:
--------------------------------------------------------------

*For clarity, this occurs only when you create the same named index referencing different columns*
_The following prevents future start-up of the cluster_
{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}




      was (Author: cdaw):
    *For clarity, this occurs only when you create the same named index referencing different columns*
_The following prevents future start-up of the cluster*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}



  
> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Issue Comment Edited] (CASSANDRA-2730) exception generate when using same index names

Posted by "Cathy Daw (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042349#comment-13042349 ] 

Cathy Daw edited comment on CASSANDRA-2730 at 6/1/11 6:44 PM:
--------------------------------------------------------------

*For clarity, this occurs only when you create the same named index referencing different columns*
* Workaround #1:  In CQLSH:  Prior to restarting server, drop this column family after you see this error, then you future restarts will be fine.
* Workaround #2: In cassandra-cli:  Prior to restarting server, run the drop index command for this index

{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}




      was (Author: cdaw):
    *For clarity, this occurs only when you create the same named index referencing different columns*
_The following prevents future start-up of the cluster.  If you immediately drop this column family after you see this error, then you future restarts will be fine._
{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}



  
> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Issue Comment Edited] (CASSANDRA-2730) exception generate when using same index names

Posted by "Cathy Daw (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042349#comment-13042349 ] 

Cathy Daw edited comment on CASSANDRA-2730 at 6/1/11 6:40 PM:
--------------------------------------------------------------

*For clarity, this occurs only when you create the same named index referencing different columns*
_The following prevents future start-up of the cluster.  If you immediately drop this column family after you see this error, then you future restarts will be fine._
{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}




      was (Author: cdaw):
    *For clarity, this occurs only when you create the same named index referencing different columns*
_The following prevents future start-up of the cluster_
{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}



  
> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Updated] (CASSANDRA-2730) exception generate when using same index names

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2730:
--------------------------------------

         Priority: Minor  (was: Major)
    Fix Version/s: 0.8.1

> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>            Priority: Minor
>              Labels: cql
>             Fix For: 0.8.1
>
>         Attachments: 2730.txt
>
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Updated] (CASSANDRA-2730) exception generate when using same index names

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2730:
--------------------------------------

    Attachment: 2730.txt

Attached patch fixes the problem, but requires CASSANDRA-2617 to be finished first.

> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>         Attachments: 2730.txt
>
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Commented] (CASSANDRA-2730) exception generate when using same index names

Posted by "Cathy Daw (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042349#comment-13042349 ] 

Cathy Daw commented on CASSANDRA-2730:
--------------------------------------

*For clarity, this occurs only when you create the same named index referencing different columns*
_The following prevents future start-up of the cluster*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}




> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Issue Comment Edited] (CASSANDRA-2730) exception generate when using same index names

Posted by "Cathy Daw (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042349#comment-13042349 ] 

Cathy Daw edited comment on CASSANDRA-2730 at 6/1/11 6:45 PM:
--------------------------------------------------------------

*For clarity, this occurs only when you create the same named index referencing different columns*
* Workaround #1:  In CQLSH:  Prior to restarting server, drop this column family after you see this error, then future server restarts will be fine.
* Workaround #2: In cassandra-cli:  Prior to restarting server, run the drop index command for this index, then future server restarts will be fine.

{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}




      was (Author: cdaw):
    *For clarity, this occurs only when you create the same named index referencing different columns*
* Workaround #1:  In CQLSH:  Prior to restarting server, drop this column family after you see this error, then you future restarts will be fine.
* Workaround #2: In cassandra-cli:  Prior to restarting server, run the drop index command for this index

{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}



  
> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Commented] (CASSANDRA-2730) exception generate when using same index names

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042385#comment-13042385 ] 

Jonathan Ellis commented on CASSANDRA-2730:
-------------------------------------------

correct

> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Commented] (CASSANDRA-2730) exception generate when using same index names

Posted by "BAONING WU (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042382#comment-13042382 ] 

BAONING WU commented on CASSANDRA-2730:
---------------------------------------

so this "drop index" is in 0.8.1? I can't find it in my 0.8.0-rc1.

> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Resolved] (CASSANDRA-2730) exception generate when using same index names

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-2730.
---------------------------------------

    Resolution: Fixed

fix rolled into CASSANDRA-2617 patch

> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>         Attachments: 2730.txt
>
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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

[jira] [Issue Comment Edited] (CASSANDRA-2730) exception generate when using same index names

Posted by "Cathy Daw (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042349#comment-13042349 ] 

Cathy Daw edited comment on CASSANDRA-2730 at 6/1/11 6:47 PM:
--------------------------------------------------------------

*For clarity, this occurs only when you create the same named index referencing different columns*
* Workaround #1:  In CQLSH:  Prior to restarting server, drop this column family after you see this error, then future server restarts will be fine.
* Workaround #2: In cassandra-cli:  Prior to restarting server, run the "drop index cf column" command for both attempts (birth_year and session_token in my example), then future server restarts will be fine.

{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}




      was (Author: cdaw):
    *For clarity, this occurs only when you create the same named index referencing different columns*
* Workaround #1:  In CQLSH:  Prior to restarting server, drop this column family after you see this error, then future server restarts will be fine.
* Workaround #2: In cassandra-cli:  Prior to restarting server, run the drop index command for this index, then future server restarts will be fine.

{code}
cqlsh> CREATE INDEX birth_year_key ON users (session_token);
Bad Request: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=cqldb,columnfamily=users.birth_year_key
{code}

*PASS: CQLSH allows multiple indexes without an issue*
{code}
cqlsh> CREATE INDEX gender_key ON users (gender);
cqlsh> CREATE INDEX state_key ON users (state);
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
{code}

*PASS: CQLSH correctly errors out creating the same index twice*
{code}
cqlsh> CREATE INDEX birth_year_key ON users (birth_year);
Bad Request: Index exists
{code}



  
> exception generate when using same index names
> ----------------------------------------------
>
>                 Key: CASSANDRA-2730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2730
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: BAONING WU
>              Labels: cql
>
> when using cqlsh tool to generate indexes, for example, suppose we have a column family Tuser, which has two columns: name and state.
> cqlsh> create index name_key on Tuser(name);
> cqlsh> create index name_key on Tuser(state);
> note that name_key is used twice by mistake, then a javax.management.InstanceAlreadyExistsException will be thrown and this exception will prevent cassandra service from starting any more.

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