Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2293D7E54 for ; Mon, 18 Jul 2011 04:53:20 +0000 (UTC) Received: (qmail 55949 invoked by uid 500); 18 Jul 2011 04:53:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55337 invoked by uid 500); 18 Jul 2011 04:53:10 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 55329 invoked by uid 99); 18 Jul 2011 04:53:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2011 04:53:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yulinyen@gmail.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-ew0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2011 04:53:03 +0000 Received: by ewy19 with SMTP id 19so1483566ewy.31 for ; Sun, 17 Jul 2011 21:52:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CtltzmPDAtmWDL/WxdOvCOIMXWYVJlV2b9TQiTFVk3M=; b=RmYzs2Wee7nUxQVbO1/6obiRdvAY3/QMqrhS5fu5T5nZmeoeNLLPTYo+CIYpEBwcuG 1ws4m6kqJGjD45tiaM0a5DypD1zTNMJYTuBTu5em38q8Ba2eNntWL6U1ale5qSoN42fk D8UM/pquQzsTAXzNI4/mHu4FP2YDLSqhFSWZo= MIME-Version: 1.0 Received: by 10.213.36.3 with SMTP id r3mr839665ebd.80.1310964761056; Sun, 17 Jul 2011 21:52:41 -0700 (PDT) Received: by 10.213.112.194 with HTTP; Sun, 17 Jul 2011 21:52:40 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Jul 2011 12:52:40 +0800 Message-ID: Subject: Re: Default behavior of generate index_name for columns... From: Boris Yen To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0015174be6d2e557b804a850c462 --0015174be6d2e557b804a850c462 Content-Type: text/plain; charset=ISO-8859-1 I have tested another case, not sure if this is a bug. I created a few column families on 0.8.0 each has user_name column, in addition, I also enabled secondary index on this column. Then, I upgraded to 0.8.1, when I used cassandra-cli: show keyspaces, I saw index name "user_name_idx" appears for different columns families. It seems the validation rule for index_name on 0.8.1 has been skipped completely. Is this a bug? or is it intentional? Regards Boris On Sat, Jul 16, 2011 at 10:38 AM, Boris Yen wrote: > Done. It is CASSANDRA-2903 > . > > On Sat, Jul 16, 2011 at 9:44 AM, Jonathan Ellis wrote: > >> Please. >> >> On Fri, Jul 15, 2011 at 7:29 PM, Boris Yen wrote: >> > Hi Jonathan, >> > Do I need to open a ticket for this? >> > Regards >> > Boris >> > >> > On Sat, Jul 16, 2011 at 6:29 AM, Jonathan Ellis >> wrote: >> >> >> >> Sounds reasonable to me. >> >> >> >> On Fri, Jul 15, 2011 at 2:55 AM, Boris Yen wrote: >> >> > Hi, >> >> > 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. >> >> > Regards >> >> > Boris >> >> > >> >> >> >> >> >> >> >> -- >> >> Jonathan Ellis >> >> Project Chair, Apache Cassandra >> >> co-founder of DataStax, the source for professional Cassandra support >> >> http://www.datastax.com >> > >> > >> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of DataStax, the source for professional Cassandra support >> http://www.datastax.com >> > > --0015174be6d2e557b804a850c462 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have tested another case, not sure if this is a bug.

I= created a few column families on 0.8.0 each has user_name column, in addit= ion, I also enabled secondary index on this column. =A0Then, I upgraded to = 0.8.1, when I used cassandra-cli: show keyspaces, I saw index name "us= er_name_idx" appears for different columns families. It seems the vali= dation rule for index_name on 0.8.1 has been skipped completely.

Is this a bug? or is it intentional?

Regards
Boris

On Sat, = Jul 16, 2011 at 10:38 AM, Boris Yen <yulinyen@gmail.com> wrote:
Done. It is=A0= CASSANDRA-2903.

On Sat, Jul 16, 2011 at 9:44 AM, Jonathan El= lis <jbellis@gmail.com> wrote:
Please.

On Fri, Jul 15, 2011 at 7:29 PM, Boris Yen <yulinyen@gmail.com> wrote:
> Hi Jonathan,
> Do I need to open a ticket for this?
> Regards
> Boris
>
> On Sat, Jul 16, 2011 at 6:29 AM, Jonathan Ellis <jbellis@gmail.com> wrote:
>>
>> Sounds reasonable to me.
>>
>> On Fri, Jul 15, 2011 at 2:55 AM, Boris Yen <yulinyen@gmail.com> wrote:
>> > Hi,
>> > I have a few column families, each has a column called user_n= ame. I
>> > tried to
>> > use secondary index on user_name column for each of the colum= n family.
>> > However, when creating these column families, cassandra keeps= reporting
>> > "Duplicate index name..." exception. I finally figu= red 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 cou= ld be like
>> > "column name"+"cf name", so the index nam= e would not collide with each
>> > other
>> > that easily, if the user do not assign "index_name"= when creating a
>> > column
>> > family.
>> > Regards
>> > Boris
>> >
>>
>>
>>
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of DataStax, the source for professional Cassandra supp= ort
>> http://www.d= atastax.com
>
>



--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.c= om


--0015174be6d2e557b804a850c462--