Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 98216 invoked from network); 20 Feb 2009 22:30:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Feb 2009 22:30:37 -0000 Received: (qmail 3987 invoked by uid 500); 20 Feb 2009 22:30:36 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 3864 invoked by uid 500); 20 Feb 2009 22:30:35 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 3853 invoked by uid 99); 20 Feb 2009 22:30:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Feb 2009 14:30:35 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of clint.a.m@gmail.com designates 209.85.198.225 as permitted sender) Received: from [209.85.198.225] (HELO rv-out-0506.google.com) (209.85.198.225) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Feb 2009 22:30:29 +0000 Received: by rv-out-0506.google.com with SMTP id k40so1089827rvb.29 for ; Fri, 20 Feb 2009 14:30:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=qWMHN4yv7YMaDrkgTmviyimNgjC3KfxTtN1GBm0UToU=; b=JWVb++r0UkyX2Sy2lJffaNi7o2/6lee/G39fAN4gfyIOmgII1pJEWGyHtKJ82nFopO 6rODyzKqkrkmyZ/6Z1yn6mkZslGR/uB0tKl9jM0tAdbHwjKBjMhwWlUOLGyN9BRu8CV3 V/yjShsxHoHLy6B3tfbg9glSiYYCDYo24LX4c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=RmewfRxR8dCjew7eveMjPfS+klIDvqLbIj1nWHCyw6kHis6M37M1+lhh8LG3KO4KB3 kpA3rMfQtimcD8i+DD+9Yo4CjIJusF+MGb/PrwwtCfgi1iKHXWAl1ZBO3jd3Q3V7PbeC gDxL02XnSyxjsOEYg7D/AOfzim8w+UFzfwY9E= MIME-Version: 1.0 Sender: clint.a.m@gmail.com Received: by 10.141.45.16 with SMTP id x16mr613893rvj.290.1235169009077; Fri, 20 Feb 2009 14:30:09 -0800 (PST) In-Reply-To: References: Date: Fri, 20 Feb 2009 14:30:09 -0800 X-Google-Sender-Auth: 8d59e46bf8349201 Message-ID: Subject: Re: Secondary index From: Clint Morgan To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd24da40610190463613235 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd24da40610190463613235 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Yeah, thats a current limitation: indexes for a table must be pre-defined. I'm at a point where I need the ability to add/modify indexes for existing tables as well, so may work on a patch in the next week or so... -clint On Fri, Feb 20, 2009 at 2:15 PM, Slava Gorelik wrote: > Hi.From secondary index test i found that index can be created only during > column family creation, is it correct ? > Is there any way to add new secondary index after column family is created > (on going) ? > > Thank You and Best Regards. > Slava. > --000e0cd24da40610190463613235--