Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 655AB44AE for ; Thu, 2 Jun 2011 16:21:01 +0000 (UTC) Received: (qmail 64875 invoked by uid 500); 2 Jun 2011 16:21:01 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 64848 invoked by uid 500); 2 Jun 2011 16:21:01 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 64840 invoked by uid 99); 2 Jun 2011 16:21:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jun 2011 16:21:00 +0000 X-ASF-Spam-Status: No, hits=4.0 required=5.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.160.41 as permitted sender) Received: from [209.85.160.41] (HELO mail-pw0-f41.google.com) (209.85.160.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jun 2011 16:20:53 +0000 Received: by pwi12 with SMTP id 12so727728pwi.14 for ; Thu, 02 Jun 2011 09:20:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=6WqyhmdF+Zf3cKJpBNUXGezqbuLZRl3IIEo8UBK7n10=; b=wxglnZ5ib3oV36sssy9/1a1Tjexkfk3+bWm4uRU/x1t+T6ge65l8lXONXhTYv6j9dL coU+/oI2BfYtsTxdat7MvqDa4DUwWp/ZlsE88xJ/GuqNqM8WzXTZXCFzDIrK+EK+o14l pFn6YrU9IlD+6BbIRS8n5OnB4t9xD639cll2I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=pO/W5yuUrkzunOEF5FW8P7ReyFj58NkH5iR4n6ypSDZmhwgWgz2Ar0IVz4pLI3gv6U r5iau5r3gv+SohtyWAuwWYWgCoK7kN7RA0zLxDPmDj16C4OtbxPRdhM401zTN20HMTBm 3ApicLrSNkbIWDiAwKcaHnA4bKlEEZV7GfjZY= MIME-Version: 1.0 Received: by 10.68.34.74 with SMTP id x10mr362500pbi.175.1307031632165; Thu, 02 Jun 2011 09:20:32 -0700 (PDT) Received: by 10.68.40.193 with HTTP; Thu, 2 Jun 2011 09:20:32 -0700 (PDT) In-Reply-To: References: Date: Thu, 2 Jun 2011 09:20:32 -0700 Message-ID: Subject: Re: Lucene's FST for the block index From: Ted Yu To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=bcaec52160e3253bad04a4bd04ae X-Virus-Checked: Checked by ClamAV on apache.org --bcaec52160e3253bad04a4bd04ae Content-Type: text/plain; charset=ISO-8859-1 Currently BlockIndex is an inner class of HFile. It would be nice to support pluggable block index implementations. FYI On Thu, Jun 2, 2011 at 9:09 AM, Jason Rutherglen wrote: > Lucene has a compact FST (Finite State Transducer) that's used for the > sorted terms index. I think this is the same type of functionality as > the HBase block index, eg, a sorted index of row ids? The FST is more > compact keeping every Nth row id in RAM. Does the HFile format allow > pluggable block index implementations? > > I posted this to Jira issues however that's probably not the best place. > --bcaec52160e3253bad04a4bd04ae--