Return-Path: 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 A30C29E5D for ; Sun, 19 Feb 2012 04:53:00 +0000 (UTC) Received: (qmail 78382 invoked by uid 500); 19 Feb 2012 04:52:59 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 77673 invoked by uid 500); 19 Feb 2012 04:52:58 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 77633 invoked by uid 99); 19 Feb 2012 04:52:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Feb 2012 04:52:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-tul01m020-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Feb 2012 04:52:51 +0000 Received: by obbta7 with SMTP id ta7so8085088obb.14 for ; Sat, 18 Feb 2012 20:52:31 -0800 (PST) Received-SPF: pass (google.com: domain of saint.ack@gmail.com designates 10.60.13.1 as permitted sender) client-ip=10.60.13.1; Authentication-Results: mr.google.com; spf=pass (google.com: domain of saint.ack@gmail.com designates 10.60.13.1 as permitted sender) smtp.mail=saint.ack@gmail.com; dkim=pass header.i=saint.ack@gmail.com Received: from mr.google.com ([10.60.13.1]) by 10.60.13.1 with SMTP id d1mr6421719oec.41.1329627151116 (num_hops = 1); Sat, 18 Feb 2012 20:52:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=O6FKrbwt+dPczlVTlZ8X7PTCL6jP+k23zs9eRGcDzu0=; b=TWfTYGfiMXewjyHMDai7yomv97Jremf4QqN4JI0fRIDbnwK5Gd3IRbbo3PLkWyqeB1 hJwsSOcHNTAuNkVLY9sOQ1nxDFn8WjY32CTUsoK268F8evOGfiBxScSrFhsx8VLfOPCg ZMNw9evvfRwAollSj+QWF+I4A3z94HANW3pko= MIME-Version: 1.0 Received: by 10.60.13.1 with SMTP id d1mr5495129oec.41.1329627151074; Sat, 18 Feb 2012 20:52:31 -0800 (PST) Sender: saint.ack@gmail.com Received: by 10.182.122.66 with HTTP; Sat, 18 Feb 2012 20:52:31 -0800 (PST) In-Reply-To: <1329342951.68878.YahooMailNeo@web130101.mail.mud.yahoo.com> References: <1329342951.68878.YahooMailNeo@web130101.mail.mud.yahoo.com> Date: Sat, 18 Feb 2012 20:52:31 -0800 X-Google-Sender-Auth: 9x1Hp2iDl3WF-Yi0HDosBwXnMLA Message-ID: Subject: Re: Pluggable storage? From: Stack To: user@hbase.apache.org, Otis Gospodnetic Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Feb 15, 2012 at 1:55 PM, Otis Gospodnetic wrote: > Hi, > > Was just reading about SSTable and LevelDB (http://www.igvita.com/2012/02= /06/sstable-and-log-structured-storage-leveldb/), which has some HBase refe= rences. =A0Somebody pointed out in comments Riak supports LevelDB as a stor= age engine option, which made me wonder whether pluggable backend storage i= s on HBase's long-term road map? > No one seems to be calling for it Otis. I think we're still working on our current storage trying to make sense of it under the different loadings. What would you want? Leveldb is attractive because its 'done' but it would seem to make for significantly more i/o spent at compaction time (though at read time there could be less). St.Ack