Presto Usage Guide

Updated at：2025-11-03

Overview

Presto, a data query engine developed by Facebook, enables fast interactive analysis of massive datasets and supports multiple data sources like Hive and relational databases. Thanks to BOS’s advantages such as ultra-low cost, high performance, reliability, and high throughput, more enterprises are turning to BOS as their big data storage solution. This document provides a brief overview of using Presto with BOS.

Prerequisites

Refer to the Hive Usage Guide to install and configure Hive

Installation and configuration

The installed version is 349, and you can refer to the process in the document Presto Deployment. Among them, if the local machine also serves as a worker, set in config.properties:

Bash

1node-scheduler.include-coordinator=true #Need to be changed to true

In etc/catalog/hive.properties, configure as follows:

                Bash
                
            

                connector.name=hive-hadoop2
 hive.config.resources=/ssd2/hadoop-3.3.2/etc/hadoop/core-site.xml,/ssd2/hadoop-3.3.2/etc/hadoop/hdfs-site.xml #The address here must be correct
hive.metastore.uri=thrift://127.0.0.1:9083
hive.allow-drop-table=false
hive.storage-format=ORC
hive.metastore-cache-ttl=1s
hive.metastore-refresh-interval=1s
hive.metastore-timeout=35m
hive.max-partitions-per-writers=1000
hive.cache.enabled=true
hive.cache.location=/opt/hive-cache
            

Copy the bos filesystem jar package to plugin/hive-hadoop2/, then run:

Bash

1./bin/launcher start

Start the presto-server,

Bash

1./presto-cli --server localhost:8881 --catalog hive --schema default

Run

                Bash
                
            

                presto:default>use hive;
 USE
 presto:hive>select * from hive_test limit 10;
     a   |    b
-------+----------
 11027 |  "11345"
 10227 |  "24281"
 32535 |  "16409"
 24286 |  "24435"
  2498 |  "10969"
 16662 |  "16163"
  5345 |  "26005"
 21407 |  "5365"
 30608 |  "4588"
 19686 |  "11831"
 (10 rows)
Query 20230601_084130_00004_dzvjb, FINISHED, 1 node
Splits: 18 total, 18 done (100.00%)
[Latency: client-side: 0:02, server-side: 0:02] [59.4K rows, 831KB] [28.9K rows/s, 404KB/s]
            

In the example above, we query data stored in BOS through Presto.

Presto access based on S3

Presto accesses data stored in BOS only via Hive, but Hive can retrieve BOS data in two ways: the first uses the previously mentioned method based on bos-hdfs, while the second accesses BOS directly through the S3 protocol.

Hive configuration

Install metastore:

                Bash
                
                wget "https://repo1.maven.org/maven2/org/apache/hive/hive-standalone-metastore/3.1.2/hive-standalone-metastore-3.1.2-bin.tar.gz"
tar -zxvf hive-standalone-metastore-3.1.2-bin.tar.gz
sudo mv apache-hive-metastore-3.1.2-bin /usr/local/metastore
sudo chown user:user /usr/local/metastore

Download and use hive-standalone-metastore, and add the necessary jar packages:

                Bash
                
            

                rm /usr/local/metastore/lib/guava-19.0.jar
cp /usr/local/hadoop/share/hadoop/common/lib/guava-27.0-jre.jar \
  /usr/local/metastore/lib/
cp /usr/local/hadoop/share/hadoop/tools/lib/hadoop-aws-3.2.1.jar \
  /usr/local/metastore/lib/
cp /usr/local/hadoop/share/hadoop/tools/lib/aws-java-sdk-bundle-1.11.375.jar \
  /usr/local/metastore/lib/
            

Then configure /usr/local/metastore/conf/metastore-site.xml.

                XML
                
            

                <property>
    <name>javax.jdo.option.ConnectionURL</name>
    <value>jdbc:mysql://localhost/metastore?createDatabaseIfNotExist=true</value>
</property>
<property>
    <name>javax.jdo.option.ConnectionDriverName</name>
    <value>com.mysql.jdbc.Driver</value>
</property>
<property>
    <name>javax.jdo.option.ConnectionUserName</name>
    <value>hive</value>
</property>
<property>
    <name>javax.jdo.option.ConnectionPassword</name>
    <value>hive</value>
</property>
<property>
    <name>hive.metastore.event.db.notification.api.auth</name>
    <value>false</value>
</property>
<property>
    <name>fs.s3a.access.key</name>
    <value>S3_ACCESS_KEY</value>
</property>
<property>
    <name>fs.s3a.secret.key</name>
    <value>S3_SECRET_KEY</value>
</property>
<property>
    <name>fs.s3a.connection.ssl.enabled</name>
    <value>false</value>
</property>
<property>
    <name>fs.s3a.path.style.access</name>
    <value>true</value>
</property>
<property>
    <name>fs.s3a.endpoint</name>
    <value>S3_ENDPOINT</value>
</property>
            

fs.s3a.endpoint It refers to the S3 endpoint. The S3 endpoint of BOS can be found in BOS S3 Domain Name.

Start hive metastore:

Bash

1/usr/local/metastore/bin/start-metastore &

Presto configuration

The version of Presto remains unchanged here, and the content of hive.properties is changed to:

                Bash
                
            

                connector.name=hive-hadoop2
hive.metastore.uri=thrift://localhost:9083
hive.s3.path-style-access=true
hive.s3.endpoint=S3_ENDPOINT
hive.s3.aws-access-key=S3_ACCESS_KEY
hive.s3.aws-secret-key=S3_SECRET_KEY
hive.s3.ssl.enabled=false
            

Start Presto

Bash

1/usr/local/trino/bin/launcher start

Create a Schema

                Bash
                
            

                CREATE SCHEMA IF NOT EXISTS hive.iris
 WITH (location = 's3a://my-bos-bucket/'); //Note that the location here starts with s3a. If the bucket is my-bos-bucket, the location should start with s3a://my-bos-bucket/
 #Create a table
CREATE TABLE IF NOT EXISTS hive.iris.iris_parquet (
  sepal_length DOUBLE,
  sepal_width  DOUBLE,
  petal_length DOUBLE,
  petal_width  DOUBLE,
  class        VARCHAR
)
WITH (
  external_location = 's3a://my-bos-bucket/iris_parquet',
  format = 'PARQUET'
);
SELECT
  sepal_length,
  class
FROM hive.iris.iris_parquet
LIMIT 10;
            

Hive Usage Guide

Spark Usage Guide