Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 79655 invoked from network); 28 Oct 2010 15:50:31 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Oct 2010 15:50:31 -0000 Received: (qmail 80425 invoked by uid 500); 28 Oct 2010 15:50:31 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 80295 invoked by uid 500); 28 Oct 2010 15:50:28 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 80277 invoked by uid 99); 28 Oct 2010 15:50:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 15:50:27 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ayyagarikiran@gmail.com designates 209.85.212.50 as permitted sender) Received: from [209.85.212.50] (HELO mail-vw0-f50.google.com) (209.85.212.50) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 15:50:20 +0000 Received: by vws4 with SMTP id 4so551358vws.37 for ; Thu, 28 Oct 2010 08:49:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=QfRDUPuYmcz9+7s9qLDwOdi2Ar6mw6g9eFoXqdupDuw=; b=Rcw9a9YpyqYo1H/RK4N/KgtlxbJZQgN4w6IFCkQCA4f1wDB5ndHOinU57xDVMD2Oro ZB4Hch5ihrhNo9VX806Fj8sQpLIPoIcxxdtI/LXz566akTS1dSJZj/ezx3mJdQ4iW+Zl pnb3MmWfnWG3okv5+hKrwYDsiORYJCeMPZLBE= 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 :content-transfer-encoding; b=XzngJ0zpqoB54/zg7Omvu3mhQhzH18tlXausKwwfajNnmFOasfPsfGx4Oz0lmmp8tW 4Q+tNkiW25fYIgzIkGCX1F2BdrXVWIn7yoaMVc9bOsk8u4MxvXEx4DpwVbHDODAXmoCS QFFk04gkz5UVrey9E/4Y8OHt8fkll6glwEOp0= MIME-Version: 1.0 Received: by 10.42.246.200 with SMTP id lz8mr8754648icb.303.1288280998864; Thu, 28 Oct 2010 08:49:58 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.231.14.72 with HTTP; Thu, 28 Oct 2010 08:49:58 -0700 (PDT) In-Reply-To: <4CC93FF5.9030900@gmail.com> References: <4CC8C64D.3040105@gmail.com> <8B0CA904-52B9-464D-8C78-BF6AA37724BB@marcelot.net> <4CC93FF5.9030900@gmail.com> Date: Thu, 28 Oct 2010 21:19:58 +0530 X-Google-Sender-Auth: i2lPd7mK-zynpuJBpzl2TrftXXA Message-ID: Subject: Re: One moe thing about the DS paths From: Kiran Ayyagari To: Apache Directory Developers List , elecharny@apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 10/28/10, Emmanuel Lecharny wrote: > On 10/28/10 9:55 AM, Kiran Ayyagari wrote: >> >>>> One small last thing : currently, indexes files are named using the >>>> Attribute OID. I find it not very friendly. Can't we use the Alias >>>> instead >>>> ? >> -1, there is a reason we changed back to OID, it is to avoid creating >> duplicate indexes >> on the same AT. >> >> If we use alias then there is no way to check them, >> e.x if user creates two indexes on "cn" and "commonName" then jdbm >> creates "cn.db" and "commonName.db" which we cannot distinguish during >> creation > We can check that using the SchemaManager, which is available when we > create the files. AT.getName() always return the first alias. we can't depend on this as the schema *might* change(e.x a custom schema) the order of aliases. Checking for the existing indexes requires to get all the *.db files and perform various checks on their names (after removing ".db") but this check needs to be performed after *every* single index instantiation >> Another case is to find which indexes are no longer needed when user >> removes them from config. > Same, using the SM will do the trick. >> We store a OID.txt file with AT's definition alongside the index files >> to let the user know what that indexed attribute is. > Do we? Never saw this file. yes, we create them > > -- > Regards, > Cordialement, > Emmanuel L=E9charny > www.iktek.com > > --=20 Kiran Ayyagari