From dev-return-145824-archive-asf-public=cust-asf.ponee.io@hive.apache.org Wed Jan 24 21:16:10 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id D3057180630 for ; Wed, 24 Jan 2018 21:16:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C377A160C3C; Wed, 24 Jan 2018 20:16:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 18669160C39 for ; Wed, 24 Jan 2018 21:16:09 +0100 (CET) Received: (qmail 21528 invoked by uid 500); 24 Jan 2018 20:16:08 -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 21375 invoked by uid 99); 24 Jan 2018 20:16:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jan 2018 20:16:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C5C7BC0C19 for ; Wed, 24 Jan 2018 20:16:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id i5-xef_mM9mI for ; Wed, 24 Jan 2018 20:16:05 +0000 (UTC) Received: from mail-qt0-f171.google.com (mail-qt0-f171.google.com [209.85.216.171]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E5A855F1B3 for ; Wed, 24 Jan 2018 20:16:04 +0000 (UTC) Received: by mail-qt0-f171.google.com with SMTP id d8so13695513qtm.0 for ; Wed, 24 Jan 2018 12:16:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=1IYZrQ4IDPdncZAgN2DUgOasQTTl+RW4Nvap2mC4Kro=; b=UPkfkhBm2HasGYEO+q3YUkUcfxczSLy44cj8+RjaZDqnTRgvipl5ieVzDsP/tps7hU aMyY01YkpYDVrJD8y3u6KihsjMWUO08GPan05fNPWaFg7bbnkFfDw9YwpxGJvz5LiisS qSt9+jmrpCP5jkPr0J714f6sP55Pr498v6UHM1saH8HX8iRA81Axwv2WXrcgZp1npNy8 5ol1+NoA9u8h6+sd338NIRlZ1AyX6jFX/OAowuhfHS0mhT8gWoxbFEX9q+3Vm3dFxFOU hO3IenhCBIXduUSHLQEc2/AVwLMUFT4QGuK5l8O1Pyv+fkRLHfttC+UAtoMSYc7yrnAU yULA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1IYZrQ4IDPdncZAgN2DUgOasQTTl+RW4Nvap2mC4Kro=; b=U+8FdEx/FzAo66qcSNNoZPWNg6+ewZffLMqZF7pNMK/HOE+qV7Uw/lsGgsPooWlq76 uVx1j0ZiWDZOsySww4B4HrGriFeYRsHqYVzLyA6qUU/MwliC9GR+wFfALmpCiXsWB+Ht ECUjnpaPNn/qJEU/rK6/JOJqzHRDW9tBUwciYIZDdQP86Q587WTwMFMlcLVpx91wbacs D06afatqlZuAejG3DnmRcKVgO3+6C+6JVcichFdpa1st9sr02hujsCJK+r/nC1RT4nn9 OS9v64hUTdgfeTCAeyyd2YmMmw2a8sQrdWR/LXw/siQIbi8BDR0MuD8dKexs+94Owmp6 JZFg== X-Gm-Message-State: AKwxytctI0/WTTPY+8rx1VhKmnMIcvVF6VUva1n+liSPstVgDcCCHwBV +cxm2giCPOtP9lVY7Tzq1UnzbX+rGVscdak2EJCEejup X-Google-Smtp-Source: AH8x224Khs9qa0fUTwr+BBLT9Stw63tF6zIscp2u4Y2iYvJ18SK0PyIiwkYB8X4Vd90ueJdhIc4s/VH6jtuKBdXb+OM= X-Received: by 10.200.35.208 with SMTP id r16mr12601318qtr.256.1516824963763; Wed, 24 Jan 2018 12:16:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.18.69 with HTTP; Wed, 24 Jan 2018 12:16:03 -0800 (PST) From: Alan Gates Date: Wed, 24 Jan 2018 12:16:03 -0800 Message-ID: Subject: Hive packaging and the standalone metastore To: dev@hive.apache.org Content-Type: multipart/alternative; boundary="001a1141196226d57605638b552f" --001a1141196226d57605638b552f Content-Type: text/plain; charset="UTF-8" In HIVE-17983 I have been working on packaing and start/stop scripts for the standalone metastore. One question this brings up is how Hive will be released now, with or without the metastore. I can see two options: 1) We continue to ship the metastore with Hive. Not only does this mean the metastore code is in the Hive source code release and the metastore jars are in the Hive binary distribution, but scripts like metastore.sh are still included in Hive's bin directory, so that Hive admins can still do 'hive --service metastore' to start the metastore. I see the following advantages of this: a) it is completely backwards compatible; b) it is what users would expect (I have installed many databases and never been asked to first install a separate package for its data catalog or any other essential piece); c) this will still be the metastore's most frequent use case for at least the near future. The disadvantage is it is error prone when Hive is set up to connect to a separate metastore. An operator could easily start the metastore in the Hive package, not realizing Hive is configured to connect to a different one. 2) We remove the metastore from the packaging completely like we do Hadoop and require the user to install it separately. The advantages and disadvantages of this exactly mirror those of option 1. Based on both the 80/20 rule (most metastore users will still be single system Hive users) and the law of least astonishment (people expect a database to have a data catalog) I vote for option 1. Anyone strongly feel we should do 2 instead? Any other options I haven't considered? Alan. --001a1141196226d57605638b552f--