22.2. Installing GeoMesa Trino

Note

GeoMesa currently supports Trino version 481.

22.2.1. Installing from the Binary Distribution

GeoMesa Trino artifacts are available for download or can be built from source. The easiest way to get started is to download the most recent binary version from GitHub.

Download and extract it somewhere convenient:

# download and unpackage the most recent distribution:
$ wget "https://github.com/locationtech/geomesa/releases/download/geomesa-6.0.0-SNAPSHOT/geomesa-trino_2.12-6.0.0-SNAPSHOT-bin.tar.gz"
$ tar xvf geomesa-trino_2.12-6.0.0-SNAPSHOT-bin.tar.gz
$ cd geomesa-trino_2.12-6.0.0-SNAPSHOT

Note

The Trino plugin JAR only bundles support for the AWS S3 filesystem and Iceberg REST and AWS Glue catalogs. To use Snowflake, Azure, GCS, or other filesystems, build a custom plugin JAR from source with the necessary JARs added as dependencies.

22.2.2. Building from Source

GeoMesa Trino may also be built from source. For more information, refer to the instructions on GitHub. The remainder of the instructions in this chapter assume the use of the binary GeoMesa Trino distribution. If you have built from source, the distribution is created in the target directory of geomesa-trino/geomesa-trino-dist.

22.2.3. Deploying the Plugin into a Trino Cluster

22.2.3.1. Install the Plugin JARs

The geomesa-trino_2.12-6.0.0-SNAPSHOT/dist/trino/ directory contains the server-side JARs that must be deployed into the Trino cluster.

The version of the plugin runtime JAR must match the version of the GeoMesa data store client JAR (usually installed in GeoServer; see below). If not, queries might not work correctly or at all.

Trino loads each subdirectory of its plugin directory (/usr/lib/trino/plugin/ in the standard layout) as an independent plugin. Extract the plugin zip file into a new subdirectory on every coordinator and worker:

unzip -d /usr/lib/trino/plugin/ geomesa-trino-plugin_2.12-6.0.0-SNAPSHOT.zip
mv /usr/lib/trino/plugin/geomesa-trino-plugin_2.12-6.0.0-SNAPSHOT /usr/lib/trino/plugin/spatial-iceberg

22.2.3.2. Define a Spatial Catalog

Next, define one or more catalogs by creating a properties file, e.g. /etc/trino/catalog/spatial_iceberg.properties. Configure it the same as an Iceberg connector, but set connector.name=spatial_iceberg. GeoMesa supports additional catalog properties - see Trino Connector Configuration for details.

For example:

connector.name=spatial_iceberg
iceberg.catalog.type=rest
iceberg.rest-catalog.uri=http://<catalog-host>:8181
iceberg.file-format=PARQUET
fs.s3.enabled=true
s3.endpoint=<s3-endpoint>
s3.region=<region>
s3.aws-access-key=<key>
s3.aws-secret-key=<secret>

Once the connectors are defined, restart all nodes in the cluster.

22.2.3.3. Verify Installation

The catalog can be verified with SHOW CATALOGS; in the Trino CLI. Spatial pruning can be verified using EXPLAIN checks as outlined in Verifying the Pruning Layers.

22.2.4. Setting up the Trino Command Line Tools

Warning

To use the Trino data store with the command line tools, you need to install the Trino plugin first. See Deploying the Plugin into a Trino Cluster.

GeoMesa comes with a set of command line tools for managing Trino features located in geomesa-trino_2.12-6.0.0-SNAPSHOT/bin/ of the binary distribution.

GeoMesa requires java to be available on the default path.

22.2.4.1. Configuring the Classpath

GeoMesa provides the ability to add additional JARs to the classpath using the environmental variable $GEOMESA_EXTRA_CLASSPATHS. GeoMesa will prepend the contents of this environmental variable to the computed classpath, giving it highest precedence in the classpath. Users can provide directories of jar files or individual files using a colon (:) as a delimiter.

For logging, see Logging Configuration for information about configuring the SLF4J implementation.

Use the geomesa-trino classpath command to print the final classpath that will be used when executing GeoMesa commands.

22.2.4.2. Running Commands

Test the command that invokes the GeoMesa Tools:

$ geomesa-trino

The output should look like this:

Usage: geomesa-trino [command] [command options]
  Commands:
  ...

For details on the available commands, see Trino Command-Line Tools.

22.2.5. Installing GeoMesa Trino in GeoServer

Warning

See GeoServer Versions to ensure that GeoServer is compatible with your GeoMesa version.

22.2.5.1. Installing GeoServer

As described in GeoMesa and GeoServer, GeoMesa implements a GeoTools-compatible data store. This makes it possible to use GeoMesa Trino as a data store in GeoServer. GeoServer’s web site includes installation instructions for GeoServer.

After GeoServer is running, you may optionally install the WPS plugin. The GeoServer WPS Plugin must match the version of your GeoServer instance. The GeoServer website includes instructions for downloading and installing the WPS plugin.

Note

If using Tomcat as a web server, it will most likely be necessary to pass some custom options:

export CATALINA_OPTS="-Xmx8g -XX:MaxPermSize=512M -Duser.timezone=UTC \
-server -Djava.awt.headless=true"

The value of -Xmx should be as large as your system will permit. Be sure to restart Tomcat for changes to take place.

22.2.5.2. Installing the GeoMesa Trino Data Store

To install the GeoMesa data store, extract the contents of the geomesa-trino-gs-plugin_2.12-6.0.0-SNAPSHOT-install.tar.gz file in geomesa-trino_2.12-6.0.0-SNAPSHOT/dist/gs-plugins/ in the binary distribution or geomesa-trino/geomesa-trino-gs-plugin/target/ in the source distribution into your GeoServer’s lib directory:

$ tar -xzvf \
  geomesa-trino_2.12-6.0.0-SNAPSHOT/dist/gs-plugins/geomesa-trino-gs-plugin_2.12-6.0.0-SNAPSHOT-install.tar.gz \
  -C /path/to/geoserver/webapps/geoserver/WEB-INF/lib

Restart GeoServer after the JARs are installed.

22.2.5.3. Install GeoMesa Processes

GeoMesa provides some WPS processes, such as geomesa:Density which is used to generate heat maps. In order to use these processes, install the GeoServer WPS plugin as described in the Installation guide.

22.2.6. Upgrading

To upgrade between minor releases of GeoMesa, the versions of all GeoMesa components must match. This means that the version of the geomesa-trino-plugin JAR installed in the Trino cluster must match the version of the geomesa-plugin JARs installed in the WEB-INF/lib directory of GeoServer.

See Upgrade Guide for more details on upgrading between versions.