Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-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 D0A028DB1 for ; Thu, 25 Aug 2011 00:49:18 +0000 (UTC) Received: (qmail 47555 invoked by uid 500); 25 Aug 2011 00:49:18 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 47489 invoked by uid 500); 25 Aug 2011 00:49:17 -0000 Mailing-List: contact user-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hive.apache.org Delivered-To: mailing list user@hive.apache.org Received: (qmail 47481 invoked by uid 99); 25 Aug 2011 00:49:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2011 00:49:17 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of heyongqiangict@gmail.com designates 209.85.210.46 as permitted sender) Received: from [209.85.210.46] (HELO mail-pz0-f46.google.com) (209.85.210.46) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2011 00:49:09 +0000 Received: by pzk32 with SMTP id 32so1783812pzk.33 for ; Wed, 24 Aug 2011 17:48:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=T3mGvCV7gZDzybvOjoOQlW/1DwfZlov78SeBBqhvpz4=; b=g/5DHPBkjYYl8NXWmRknAopNL7uoTRzp57Lvz5D5qcejuRopwDVje6G57wZs7H+E8k kFMHezZe81sNA9DCAe1Y2/xhYa7A6l2F9jzkmA2cZ/eQckvA2r0N/maMbI/XXCbV+8KM 0nFWMkq8yB75aNWvDcXAp3jK4gbxhuiAcaR04= MIME-Version: 1.0 Received: by 10.142.207.19 with SMTP id e19mr2852723wfg.312.1314233328422; Wed, 24 Aug 2011 17:48:48 -0700 (PDT) Received: by 10.142.208.12 with HTTP; Wed, 24 Aug 2011 17:48:48 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Aug 2011 17:48:48 -0700 Message-ID: Subject: Re: Local and remote metastores From: yongqiang he To: user@hive.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Are there features that are only provided by the remote datastore (like authorization)? No. All features should be provided by both. In the case of authorization, the problem is that it did not get fully tested with a remote metastore. So you saw some small bugs when running authorization on a remote metastore. Thanks Yongqiang On Wed, Aug 24, 2011 at 5:37 PM, Ashutosh Chauhan wr= ote: > Alex, > Difference between the two is that in case of local metastore, hive clien= t > communicates directly to the mysql while in case of remote metastore, hiv= e > client first talks to a remote metastore which in turns talks to mysql. I= n > terms of feature-set they are identical. > Hope it helps, > Ashutosh > > On Mon, Aug 22, 2011 at 09:03, Alex Holmes wrote: >> >> Hi everyone, >> >> Does anyone know the differences between local and remove Hive >> metastores? =A0Are there features that are only provided by the remote >> datastore (like authorization)? =A0Is the use of a local metastore >> recommended in production? >> >> Many thanks, >> Alex > >