Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-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 3B1AC10656 for ; Fri, 23 Jan 2015 19:12:22 +0000 (UTC) Received: (qmail 53761 invoked by uid 500); 23 Jan 2015 19:12:22 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 53693 invoked by uid 500); 23 Jan 2015 19:12:22 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 53680 invoked by uid 99); 23 Jan 2015 19:12:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2015 19:12:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_IMAGE_RATIO_08,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gates@hortonworks.com designates 209.85.220.44 as permitted sender) Received: from [209.85.220.44] (HELO mail-pa0-f44.google.com) (209.85.220.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2015 19:11:54 +0000 Received: by mail-pa0-f44.google.com with SMTP id rd3so9344956pab.3 for ; Fri, 23 Jan 2015 11:10:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=mnYK9/gi5amb/c4oOxsKPt9Ln+CSg9NWUKKr5yLIL8A=; b=af+9fUqTQxHTeRmieHJQRFQtuXEcYxNyInaocxCVkXLHdAH2TpKVqRwrpJe3/LhCsy S+Ir+00UxASNawo606uKzNHEl2pisAc7GmyIeNgfeGqi/qSz4k2od5pCRry+5foG3N1k VDCmqSVOeYddwNtX8LNHqX0oth0M9muO4biP5xiQ8cr1pSUol9lkc3K4x3Fpd10FbNkj JB7t3VgWDgdhpceVoqQHDZOhz5SAANJwrR1bKyvTfjWT1LQAnUaJdu63WW40eT+gUPny iePU0ZPf7oP2Cvp2FWqQC5wP/MXy2Z6dX1OZU3rHPchBgl1CS05wGfBe47ixMKqofpYj h4hg== X-Gm-Message-State: ALoCoQlrXIUIY3oA4QkMI6tGZMf0BfbXOttfnBMW62jgIlF+DyHH0X7wfel09d8pqfaNBTY1br9CEsm83AXTRpjm+66sz0FnoNu/fsiw2hoxTTCjvrBYj/g= X-Received: by 10.70.129.48 with SMTP id nt16mr13400231pdb.113.1422040222688; Fri, 23 Jan 2015 11:10:22 -0800 (PST) Received: from Alan-Gatess-MacBook-Pro.local (c-76-103-170-145.hsd1.ca.comcast.net. [76.103.170.145]) by mx.google.com with ESMTPSA id ok6sm2625262pdb.96.2015.01.23.11.10.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Jan 2015 11:10:21 -0800 (PST) Message-ID: <54C29C9A.8020703@hortonworks.com> Date: Fri, 23 Jan 2015 11:10:18 -0800 From: Alan Gates User-Agent: Postbox 3.0.11 (Macintosh/20140602) MIME-Version: 1.0 To: dev@hive.apache.org Subject: Re: Creating a branch for hbase metastore work References: <54C1AF98.5040708@hortonworks.com> In-Reply-To: Content-Type: multipart/related; boundary="------------000004010107070808040205" X-Virus-Checked: Checked by ClamAV on apache.org --------------000004010107070808040205 Content-Type: multipart/alternative; boundary="------------010708030908090209060401" This is a multi-part message in MIME format. --------------010708030908090209060401 Content-Type: text/plain; charset=UTF-8; format=flowed I've created a new branch hive-metastore for this work and filed HIVE-9452 as the umbrella JIRA for this work. Alan. > Edward Capriolo > January 23, 2015 at 8:59 > A while back the datastax people did this for brisk + cassandra. We should > probably make this pluggable so it works with nosql beyond hbase. > > > Nick Dimiduk > January 22, 2015 at 22:48 > +1 > > > Brock Noland > January 22, 2015 at 21:58 > +1 > Alan Gates > January 22, 2015 at 18:19 > I've been working on a prototype of using HBase to store Hive's > metadata. Basically I've built a new implementation of RawStore that > writes to HBase rather than DataNucleus. I want to see if I can build > something that has a much more straightforward schema than DN and that > is much faster. > > I'd like to get this out in public so other can look at it and > contribute, but it's no where near ready for real time. So I propose > to create a branch and put the code there. Any objections? > > Alan. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --------------010708030908090209060401 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've created a new branch= =20 hive-metastore for this work and filed HIVE-9452 as the umbrella JIRA=20 for this work.

Alan.

= = =20 January 23, 2015= =20 at 8:59
A while back the datastax= =20 people did this for brisk + cassandra. We should
probably make this=20 pluggable so it works with nosql beyond hbase.

Nick Dimiduk = =20 January 22, 2015= =20 at 22:48
+1


= = =20 January 22, 2015= =20 at 21:58
+1
Alan Gates = =20 January 22, 2015= =20 at 18:19
I've been working on a=20 prototype of using HBase to store Hive's=20 metadata.=C2=A0 Basically I've built a new implementation of RawStore that= =20 writes to HBase rather than DataNucleus.=C2=A0 I want to see if I can build= =20 something that has a much more straightforward schema than DN and that=20 is much faster.

I'd like to get this out in public so other can look at it and=20 contribute, but it's no where near ready for real time.=C2=A0 So I propose = to =20 create a branch and put the code there.=C2=A0 Any objections?

Alan.

CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u. --------------010708030908090209060401-- --------------000004010107070808040205--