

EmbeddedDriver Derby embeded JDBC driver class. Jdbc:derby: databaseName=metastore_db create=true Derby database located at current working directory In this, metastore server run in a separate process to the Hive service.īelow is the high level architecture of three different Hive metastores:īelow are the configuration properties and their default values which will control the above metastore setups. Remote Metastore: In remote metastore, all Hive Clients will make a connection to a metastore server (MySQL or PostgreSQL or Oracle) which in turn queries the datastore.In this mode, multiple users can open connection to metastore and make SQL queries against it. Local Metastore: In local metastore, a standalone database (MySQL or PostgreSQL or any other db with JDBC driver) is used as a metastore.So, embedded metastore is not practical solution but can be used for unit tests. But we can only have one Hive session open at a time that shares the same metastore. Trying to start a second session gives the error: It is a simple way to get started with Hive. Embedded metastore: Derby is the default database for the embedded metastore.There are 3 different ways to setup the metastore server using different Hive configurations:.By default, the metastore service runs in the same JVM as the Hive service and contains an embedded Derby database instance backed by the local disk.In Hive, metastore is the central repository to store metadata for hive tables/partitions. Any datastore that has a JDBC driver can be used as a metastore.To Maintain a single copy of Embedded Metastore:.
