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 EAA047B1A for ; Mon, 18 Jul 2011 05:21:31 +0000 (UTC) Received: (qmail 77342 invoked by uid 500); 18 Jul 2011 05:21:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 77141 invoked by uid 500); 18 Jul 2011 05:21:18 -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 77133 invoked by uid 99); 18 Jul 2011 05:21:16 -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 05:21:16 +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 05:21:10 +0000 Received: by ewy19 with SMTP id 19so1488813ewy.31 for ; Sun, 17 Jul 2011 22:20:49 -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=GJniV2giOpvA/zsOkWO5Mc6TKFYwE8g2GL02aeTGAE0=; b=wKfR9k7DlLLfQwmKLmpRc2AkWsGqfpDZxoMbZtTIIY9Ld0KT2oss14Ake8fvj7f+PA PWYqP1Pz3Y5kZPIYLXmxh6BvbMEnhjS7CYzWbsXF4+Q28hGpouvdS/2glDP+Xnbp6/35 1F8WaJKDu7ek8vh0I6CK/l/9Bol2GnfsI+xjY= MIME-Version: 1.0 Received: by 10.213.36.3 with SMTP id r3mr845804ebd.80.1310966448118; Sun, 17 Jul 2011 22:20:48 -0700 (PDT) Received: by 10.213.112.194 with HTTP; Sun, 17 Jul 2011 22:20:48 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Jul 2011 13:20:48 +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=0015174be6d273db2f04a851293f --0015174be6d273db2f04a851293f Content-Type: text/plain; charset=ISO-8859-1 Will this have any side effect when doing a get_indexed_slices or when a user wants to drop an index by any means? Boris On Mon, Jul 18, 2011 at 1:13 PM, Jonathan Ellis wrote: > 0.8.0 didn't check for name conflicts correctly. 0.8.1 does, but it > can't fix the ones 0.8.0 allowed, retroactively. > > On Sun, Jul 17, 2011 at 11:52 PM, Boris Yen wrote: > > 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 > >> > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com > --0015174be6d273db2f04a851293f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Will this have any side effect when doing a get_indexed_slices or when a us= er wants to drop an index by any means?

Boris

On Mon, Jul 18, 2011 at 1:13 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
0.8.0 didn't check for name conflicts c= orrectly. =A00.8.1 does, but it
can't fix the ones 0.8.0 allowed, retroactively.

On Sun, Jul 17, 2011 at 11:52 PM, Boris Yen <yulinyen@gmail.com> wrote:
> 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. =A0Then, I up= graded
> to 0.8.1, when I used cassandra-cli: show keyspaces, I saw index name<= br> > "user_name_idx" appears for different columns families. It s= eems 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 <yulinyen@gmail.com> wrote:
>>
>> Done. It is=A0CASSANDRA-2903.
>> On Sat, Jul 16, 2011 at 9:44 AM, Jonathan Ellis <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_name. I
>>> >> > tried to
>>> >> > use secondary index on user_name column for each= of the column
>>> >> > family.
>>> >> > However, when creating these column families, ca= ssandra keeps
>>> >> > reporting
>>> >> > "Duplicate index name..." exception. I= finally figured out that it
>>> >> > seems
>>> >> > the
>>> >> > default index name is "column name"+&q= uot;_idx", this make my column
>>> >> > family
>>> >> > violate the "uniqueness of index name"= rule.
>>> >> > I was wondering if the default index_name genera= ting 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 "ind= ex_name" when creating a
>>> >> > column
>>> >> > family.
>>> >> > Regards
>>> >> > Boris
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Jonathan Ellis
>>> >> Project Chair, Apache Cassandra
>>> >> co-founder of DataStax, the source for professional C= assandra support
>>> >> http://www.datastax.com
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Jonathan Ellis
>>> Project Chair, Apache Cassandra
>>> co-founder of DataStax, the source for professional Cassandra = support
>>> http://w= ww.datastax.com
>>
>
>



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

--0015174be6d273db2f04a851293f--