Return-Path: 
 <user-return-44107-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-user-archive@www.apache.org
Delivered-To: apmail-hbase-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 8D7AB11D53
	for <apmail-hbase-user-archive@www.apache.org>;
 Mon, 14 Jul 2014 18:15:09 +0000 (UTC)
Received: (qmail 42369 invoked by uid 500); 14 Jul 2014 18:15:07 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 42294 invoked by uid 500); 14 Jul 2014 18:15:07 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 42279 invoked by uid 99); 14 Jul 2014 18:15:06 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 18:15:06 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of varun@pinterest.com
 designates 209.85.214.173 as permitted sender)
Received: from [209.85.214.173] (HELO mail-ob0-f173.google.com)
 (209.85.214.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 18:15:02 +0000
Received: by mail-ob0-f173.google.com with SMTP id vb8so4380549obc.32
        for <user@hbase.apache.org>; Mon, 14 Jul 2014 11:14:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=pinterest.com; s=google;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=fkuTKQ1nZyf9z2rIpSYPPPPKWni1lxBT1GXXbhCWS9Y=;
        b=d4nO5iquJWnCnRPlSMrjBhKg3B+mL3PHbzzE00lgXwbpr67kAVD6ffgBW3yf6qKeIv
         tahQyqxRq/Kpe/LryLk4JUYXx9FmvK6WeSzc/MV9azgx8yCGhH8K3uy+ceebZEX01Mq7
         M1APQLl29T3nk0bTrw/iOF3rYHA445Q5ztDnQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=fkuTKQ1nZyf9z2rIpSYPPPPKWni1lxBT1GXXbhCWS9Y=;
        b=RYTwzDsGzy46m5vhPE73rz/2U/B5dIHLfuZ7aWF89U8ug8PpiUc3I62JGujBtohbZR
         fFshhSDXK0zOcmpK6LvOhZouwGkKloj7c5hXomgHruKDo7AE3/mx05nw6x8YfCi0r5p4
         BgTtV30y5iXLF5cOz8qqex2E47xu2qx6xlBVEqTE74YuTjpT98rUJmNtVUBO13AVZKnW
         zxTB9QPh0gxsiuuWph1s6dt76QxrmD2j8906xm6FmJyCTFBNqw95wREEjVvaudRgBtMV
         bn8TSgf4ko8Gev1jsTxsqNdG3JYob78nwIxp7lu5RVU6kjgh60AORVf+4ueugWl7yKg9
         BLvQ==
X-Gm-Message-State: 
 ALoCoQmeLgY/dRtxGqJuJI+ryWHU90g/MhSUpKEDD/KwFu3/sucrDCoLuxp+yB7nouX4J+naHhQX
MIME-Version: 1.0
X-Received: by 10.60.58.41 with SMTP id n9mr5048099oeq.73.1405361681790; Mon,
 14 Jul 2014 11:14:41 -0700 (PDT)
Received: by 10.76.2.44 with HTTP; Mon, 14 Jul 2014 11:14:41 -0700 (PDT)
Date: Mon, 14 Jul 2014 11:14:41 -0700
Message-ID: 
 <CAKxWWm0dMSby1+_xn6zz75AvUVDdDJV4wUAWVJFPtMdzkkxENQ@mail.gmail.com>
Subject: Question about HFile indices
From: Varun Sharma <varun@pinterest.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>,
 "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e0158add4d3102604fe2b4355
X-Virus-Checked: Checked by ClamAV on apache.org

--089e0158add4d3102604fe2b4355
Content-Type: text/plain; charset=UTF-8

Hi folks,

I am wondering why we have a tiered index in the HFile format. Is it
because the root index must fit in memory - hence must be limited in size.
Does the bound on the root index pretty much dictate the index tiers ?

Thank
Varun

--089e0158add4d3102604fe2b4355--