Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 17 Sep 2013 01:21:52 +0000 (UTC)
From: "Sergey Shelukhin (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12668923.1379380893636.144088.1379380912837@arcas>
In-Reply-To: <JIRA.12668923.1379380893636@arcas>
References: <JIRA.12668923.1379380893636@arcas>
Subject: [jira] [Created] (HIVE-5299) allow exposing metastore APIs from
 HiveServer2 with embedded metastore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sergey Shelukhin created HIVE-5299:
--------------------------------------

             Summary: allow exposing metastore APIs from HiveServer2 with embedded metastore
                 Key: HIVE-5299
                 URL: https://issues.apache.org/jira/browse/HIVE-5299
             Project: Hive
          Issue Type: New Feature
          Components: HiveServer2, Metastore
            Reporter: Sergey Shelukhin


There are (at least) two reasons to run metastore as a standalone service, rather than embedding it - access by non-hive clients, as well as miscellaneous advantages of a central service such as DB connection caching, etc.
If HiveServer2 is used, as far as I see, the latter do not require a standalone metastore (there's already a central service into which metastore could be embedded).
However, the former still does.
We should consider exposing metastore APIs from HiveServer2 (configurable on/off)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira