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 99C743D77 for ; Thu, 28 Apr 2011 09:33:06 +0000 (UTC) Received: (qmail 18343 invoked by uid 500); 28 Apr 2011 09:33:04 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 18314 invoked by uid 500); 28 Apr 2011 09:33:04 -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 18305 invoked by uid 99); 28 Apr 2011 09:33:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2011 09:33:04 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a78.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2011 09:32:57 +0000 Received: from homiemail-a78.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a78.g.dreamhost.com (Postfix) with ESMTP id E350C15C059 for ; Thu, 28 Apr 2011 02:32:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; q=dns; s=thelastpickle.com; b=dLb1+7C8UZ C3QshCXNtjlLLMpzoT+Y5XSaLO+xYa4oGNkVUD3D+v9jQyK3BjIzoZOlVT17SZqL gMLSlQQDVYjt4teoY/g1sJLmi8oUF/cmQ07RbTcz30XN/+j31jmqUZyKPWgNskkf nW03STeNLwQ6ICUqOCNn5QeYESDFo+2mY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; s=thelastpickle.com; bh=1Vgn/eq4b0DMfVIN ArTmyoa9bww=; b=VdkvB2a+jhRuxBK4lyvfYH1+g2SteHHI3sbZK7ovEkN0BzID fWswmaUo37RNqz7dArKMDbIF3uPNOHqxmnxgpzspRJoDIZlSpFREG0kVBOz4rJCS 9nnrEr6234NGFDpLmjckk1xqftVnyu5xWT0SJyVtmQqoMlZ6ZZdQadBuxtY= Received: from [10.0.1.155] (121-73-157-230.cable.telstraclear.net [121.73.157.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a78.g.dreamhost.com (Postfix) with ESMTPSA id 0314E15C062 for ; Thu, 28 Apr 2011 02:32:34 -0700 (PDT) From: aaron morton Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-1--741564451 Subject: Re: Dropping a built in secondary index on a CF Date: Thu, 28 Apr 2011 21:32:29 +1200 In-Reply-To: To: user@cassandra.apache.org References: Message-Id: <13DA23A3-071D-4F29-8F7D-0671BB01BC35@thelastpickle.com> X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-1--741564451 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I can confirm thats the way the code works when processing the CF = update. Everything is tidied up. A On 28 Apr 2011, at 18:50, Roshan Dawrani wrote: > On Thu, Apr 28, 2011 at 9:56 AM, Xaero S wrote: >=20 > You just need to use the update column family command on the = cassandra-cli and specify the columns and their metadata. To get the = metadata of the columns in the CF, you can do describe keyspace = . Keep in mind that, in your update CF command, the other = columns that must continue to have the secondary index must be = specified, otherwise, your data goes bad. >=20 > Thank you. > =20 > Request the community to correct me if i am wrong. >=20 > I will just wait for a little confirmation if someone has tried it. >=20 > For these built-in secondary indexes, another Column Family is created = behind the scenes, isn't it? Will that be automatically dropped when I = update the column meta data to drop an index and keep others? >=20 > --=20 > Roshan > Blog: http://roshandawrani.wordpress.com/ > Twitter: @roshandawrani > Skype: roshandawrani >=20 --Apple-Mail-1--741564451 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii I can confirm thats the way the code works when processing the CF update. Everything is tidied up.

A

On 28 Apr 2011, at 18:50, Roshan Dawrani wrote:

On Thu, Apr 28, 2011 at 9:56 AM, Xaero S <xaeros.s1@gmail.com> wrote:

You just need to use the update column family command on the cassandra-cli and specify the columns and their metadata. To get the metadata of the columns in the CF, you can do describe keyspace <keyspacename>. Keep in mind that, in your update CF command, the other columns that must continue to have the secondary index must be specified, otherwise, your data goes bad.

Thank you.
 
Request the community to correct me if i am wrong.

I will just wait for a little confirmation if someone has tried it.

For these built-in secondary indexes, another Column Family is created behind the scenes, isn't it? Will that be automatically dropped when I update the column meta data to drop an index and keep others?

--
Roshan
Blog: http://roshandawrani.wordpress.com/
Twitter: @roshandawrani
Skype: roshandawrani


--Apple-Mail-1--741564451--