cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2617) Add "DROP INDEX" command to CQL
Date Wed, 01 Jun 2011 15:14:58 GMT


Jonathan Ellis commented on CASSANDRA-2617:


This approach is fine for the cli (since we expect to not need it much longer) but we need
to be more forward-thinking for CQL. The reason that relational databases all do DROP based
on index name is, indexes can cover multiple columns so the by-column approach doesn't generalize.

But, I understand the motivation here, because


making this the only option right now would suck because we don't auto-generate an index name
when none is provided. (We sort of do, to create a file name for the sstables, but this is
not interchangable with an actual index name.)

I think the right thing to do here is to do some deeper surgery, and create index names when
none is provided so that can be the only thing we check for DROP.

The default index name should be comparator.getString( + "_idx" *when creating new
indexes.* When inflating old ones in CFMD.inflate, we should default them to ByteBufferUtil.bytesToHex(
to preserve compatibility in CFMD.indexColumnFamilyName (see also the TODO there).

> Add "DROP INDEX" command to CQL
> -------------------------------
>                 Key: CASSANDRA-2617
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>             Fix For: 0.8.1
>         Attachments: CASSANDRA-2617.patch

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message