Deploying the Presto Connector and a Trino Cluster on Bare Metal or in VMs
You can run the Presto connector and a Trino cluster on bare-metal servers or in virtual machines.
- Aerospike Database Enterprise Edition version 5.2 or later is required.
- Ensure that the feature key for Aerospike Connect for Presto is installed on each node of your Aerospike cluster.
- To use secondary index (SI) query support you need Aerospike server 6.0 or later.
- If you are using Trino (formerly known as PrestoSQL), ensure that you are using a compatible version of the the Presto connector.
To install the Presto connector and start it, follow these steps:
Download the installation package
Download the installation package for Aerospike Connect for Presto and extract the content to a temporary folder.
On each node of your Presto cluster, follow these steps:
.jarfiles from the
plugin/aerospikefolder under the Presto installation root.
Create the file
<Presto_dir>/etc/catalog/aerospike.propertiesto mount the
aerospikeconnector as the
<Presto_dir>is the installation directory for Presto. If you plan to query more than one Aerospike database or federate queries across Aerospike databases, add additional properties files, one for each cluster, each with a different name, such as
Add these lines to the file:
(Optional) Specify the Presto schemas that correspond to the Aerospike sets your client applications will query. By default, the Presto connector uses heuristics to rapidly infer schemas without requiring you to specify them. However, you can choose to provide the schemas.
Restart each node in your Presto cluster
What to do next
Run test queries against your Aerospike database by using the Presto CLI, which you can install from here. For examples of how to do this, see Examples of Querying Aerospike Databases with the Presto CLI.
After testing, you can connect to Presto by using the business-intelligence or visualization tool of your choice, such as Tableau Desktop (version 2020.3 or later) or Jupyter Notebook, and start your analysis of data in Aerospike.
No matter which tool you use for your data analysis, remember that:
- You must use the name you catalogued for your Aerospike database as the name of the Presto catalog. This name is also used for the
.propertiesfile in which configuration properties are set for the interactions between your Aerospike database and the Presto connector.
- You must use the name of the Aerospike namespace where your data resides as the name of the Presto schema.
- Sets in Aerospike correspond to tables in Presto.