Hive connector in Trino can retrieve data from both HDFS and S3 compatible storages. The connector requests Hive metastore as a link to those storages. There are two types of metastores. The first one is beefy one which includes multiple services. The second one is light weight and is called standalone metastore. It contains only Hive service. The standalone metastore is used to connect to S3 compatible storages.

When there is one S3 endpoint, a coordination or another server can host Hive standalone metastore. In case of many S3 endpoints, it is requested to have a Hive metastore for each endpoint. It is possible to dedicate one metastore but it should be applied a special Apache Ranger setup to separate each S3 endpoint.

To save resources, a coordinator might be used to set up Hive standalone meatostores. Docker containers host those Hive metastores. This configuration simplifies setup and maintenance of a Trino cluster.

The sample is based on Starburst 343-e open source distribution with RPM installation, Hive standalone metastoere 3.1.2, MinIO S3 storage, and RHEL 7 Linux distribution.

1. Install Docker

See Install Docker CE Edition in CentOS/RHEL 7 article.

2. Create Docker working folder

Log in to a Docker host with sudo user.

mkdir docker_hive
cd docker_hive

3. Download and prepare requested software

  • Hive standalone metastore 3.1.2

    tar -xvf hive-standalone-metastore-3.1.2-bin.tar.gz
    rm -f hive-standalone-metastore-3.1.2-bin.tar.gz
    mv apache-hive-metastore-3.1.2-bin metastore
  • Hadoop 3.2.1

    tar -xvf hadoop-3.2.1.tar.gz
    rm -f hadoop-3.2.1.tar.gz
  • JDBC connector

    Option #1. Postgres backend. Replace postgresql-.jar with the latest one.


    Option #2. MySQL backend. Replace mysql-connector-java-.el7.noarch.rpm with the latest one. MySQL connector is included in the RPM package, so after installation, the connector can be found in /usr/share/java folder.

    yum install mysql-connector-java-8.0.21-1.el7.noarch.rpm
    cp /usr/share/java/mysql-connector-java.jar ./

    There are more options for a backend but those two are tested. See Resources section below.

4. Install backend server and create a database

A backend server can be installed on coordinator or another box.

A database can be created, for example,

  • Postgres

    Using pgAdmin GUI tool.

  • MySQL

    Commndline mysql tool

    mysql -u root -p
    create database metastore;

The database name might be metastore.

5. Request corporate Certificate Authority PEM file

Copy ca.pem file to docker_hive working folder.

6. Create Dockerfile

FROM centos:7

ENV container docker

LABEL maintainer="your name here"

# copy Certificate Authority file
COPY ca.pem /etc/pki/ca-trust/source/anchors/

# copy Hive standalone package
COPY metastore /opt/metastore/

# copy Hadoop package
COPY hadoop-3.2.1 /opt/hadoop-3.2.1/

# copy Postgres or MySQL JDBC connector
COPY postgresql-42.2.16.jar /opt/metastore/lib/

# add Certificate Authority to database
RUN update-ca-trust

WORKDIR /install

# install Java 1.8 and clean cache
RUN yum install -y java-1.8.0-openjdk-devel \
  && yum clean all

# environment variables requested by Hive metastore
ENV JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk
ENV HADOOP_HOME=/opt/hadoop-3.2.1

# replace a library and add missing libraries
RUN rm -f /opt/metastore/lib/guava-19.0.jar \
  && cp ${HADOOP_HOME}/share/hadoop/common/lib/guava-27.0-jre.jar /opt/metastore/lib \
  && cp ${HADOOP_HOME}/share/hadoop/tools/lib/hadoop-aws-3.2.1.jar /opt/metastore/lib \
  && cp ${HADOOP_HOME}/share/hadoop/tools/lib/aws-java-sdk-bundle-1.11.375.jar /opt/metastore/lib

WORKDIR /opt/metastore

# copy Hive metastore configuration file
COPY metastore-site.xml /opt/metastore/conf/

# Hive metastore data folder
VOLUME ["/user/hive/warehouse"]

# create metastore backend tables and insert data. Replace postgres with mysql if MySQL backend used
RUN bin/schematool -initSchema -dbType postgres

CMD ["/opt/metastore/bin/start-metastore"]

In case of creating more than one Hive metastore, replace VOLUME ["/user/hive/warehouse"] path. Data is not supposed to be stored in that folder as MinIO or S3 compatible storage is aimed as a data storage.

7. Create Hive metastore setup file

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
        <value>MinIO URL:9000</value>
        <value>jdbc:postgresql://Backend URL or name:30684/metadata?allowPublicKeyRetrieval=true&amp;useSSL=false&amp;serverTimezone=UTC</value>
        <value>Backend user name</value>
        <value>Backend user password</value>
        <description>Thrift URI for the remote metastore. Used by metastore client to connect to remote metastore.</description>
  • Replace AccessKey with MinIO access key.
  • Replace SecretKey with MinIO secret key.
  • Make fs.s3a.connection.ssl.enabled property true if MinIO is secured with HTTPS protocol otherwise false.
  • Replace MinIO URL:9000 with MinIO address and port.
  • Replace Backend URL or name:30684 with backend address and port. If it is installed on a coordinator, use localhost.
  • If MySQL is used as backend, replace javax.jdo.option.ConnectionURL property with jdbc:mysql://Backend URL or name:3306/metastoretrino?allowPublicKeyRetrieval=true&amp;useSSL=false&amp;serverTimezone=UTC.
  • If MySQL is used as backend, replace javax.jdo.option.ConnectionDriverName property with com.mysql.cj.jdbc.Driver.
  • Replace Backend user name with backend user name.
  • Replace Backend user password with backend user password.
  • Replace /user/hive/warehouse value metastore.warehouse.dir property in to match with VOLUME ["/user/hive/warehouse"]Dockerfile.
  • If more than one Hive metastore, add metastore.warehouse.dir and metastore.thrift.port properties, for example,

8. Create Docker image

docker build -t minio_hiveimage  .

The command adds tables to backend database as well.

9. Run Hive metastore

docker run -d -p 9083:9083/tcp --name mini_hive minio_hiveimage

if more than one metastore, replace port for next metastore.

docker run -d -p 9084:9084/tcp --name mini_hive2 minio_hiveimage2

10. Test metastore

  • Add Hive connector for MinIO storage, for example, minio_connector. See Access MinIO S3 Storage in Trino with Hive Metastore article. It is a catalog level in Trino hierarchy.

  • Create a backet to store your schema, for example, finance-department.

  • Create a schema

    CREATE SCHEMA minio_connector.finance_department
    WITH (
       location = 's3a://finance-department/'

    Use dash (-) in the MinIO bucket name and underscore (_) in the schema name.

  • Create a table

    CREATE TABLE minio_connector.finance_department.test_table (col1 varchar, col2 varchar);
  • Insert values to the test table

    INSERT INTO minio_connector.finance_department.test_table
    SELECT 'value1.1', 'value1.2';

Everything has to be completed without any error messages and finance_department bucket will conatain test_table folder with a file.


  • Hive metastore accessible

    Validate if Hive metastore is visible from a coordinator and workers.

    curl -v telnet://


    *   Trying xx.x.xx.xx:9083...
    * Connected to (xx.x.xx.xx) port 9083 (#0)


    *   Trying xx.x.xx.x:9...
    * connect to xx.x.xx.xx port 3 failed: Connection refused
    * Failed to connect to port 3 after 0 ms: Connection refused
    * Closing connection 0
    curl: (7) Failed to connect to port 3 after 0 ms: Connection refused
  • Troubleshooting Access to HTTP/HTTPS Resources in Docker



comments powered by Disqus