cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boris Yen (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2903) Default behavior of generating index_name for columns might need to be improved.
Date Wed, 20 Jul 2011 06:02:00 GMT


Boris Yen commented on CASSANDRA-2903:

Personally, I won't strongly against blocking users from using 0.8.1, if they do not fix the
index_name first. As long as the message is clear enough for the user to know what to do in
order to use 0.8.1.

However, since you have allowed the user to use 0.8.1 without changing the index_name first,
I think at least the default rule for generating default index_name should not create identical
index_name not only because it might cause a violation of the rule inside 0.8.1 but also might
cause issue when a user tries to drop index column.

> Default behavior of generating index_name for columns might need to be improved.
> --------------------------------------------------------------------------------
>                 Key: CASSANDRA-2903
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.1
>            Reporter: Boris Yen
>            Assignee: Jonathan Ellis
>             Fix For: 0.8.2
>         Attachments: 2903.txt
> I have a few column families, each has a column called user_name. I tried to use secondary
index on user_name column for each of the column family. However, when creating these column
families, cassandra keeps reporting "Duplicate index name..." exception. I finally figured
out that it seems the default index name is "column name"+"_idx", this make my column family
violate the "uniqueness of index name" rule.
> I was wondering if the default index_name generating rule could be like "column name"+"cf
name", so the index name would not collide with each other that easily, if the user do not
assign "index_name" when creating a column family.

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


View raw message