Trino is a fast distributed SQL query engine for big data analytics.
See the User Manual for deployment instructions and end user documentation.
See DEVELOPMENT for information about code style, development process, and guidelines.
See CONTRIBUTING for contribution requirements.
Trino is a standard Maven project. Simply run the following command from the project root directory:
./mvnw clean install -DskipTests
On the first build, Maven downloads all the dependencies from the internet
and caches them in the local repository (
~/.m2/repository), which can take a
while, depending on your connection speed. Subsequent builds are faster.
Trino has a comprehensive set of tests that take a considerable amount of time to run, and are thus disabled by the above command. These tests are run by the CI system when you submit a pull request. We recommend only running tests locally for the areas of code that you change.
After building Trino for the first time, you can load the project into your IDE
and run the server. We recommend using
IntelliJ IDEA. Because Trino is a standard
Maven project, you easily can import it into your IDE. In IntelliJ, choose
Open Project from the Quick Start box or choose Open
from the File menu and select the root
After opening the project in IntelliJ, double check that the Java SDK is properly configured for the project:
The simplest way to run Trino for development is to run the
class. It will start a development version of the server that is configured with
the TPCH connector. You can then use the CLI to execute queries against this
server. Many other connectors have their own
*QueryRunner class that you can
use when working on a specific connector.
Trino comes with sample configuration that should work out-of-the-box for development. Use the following options to create a run configuration:
-ea -Dconfig=etc/config.properties -Dlog.levels-file=etc/log.properties -Djdk.attach.allowAttachSelf=true
The working directory should be the
trino-server-dev subdirectory. In
$MODULE_DIR$ accomplishes this automatically.
Start the CLI to connect to the server and run SQL queries:
Run a query to see the nodes in the cluster:
SELECT * FROM system.runtime.nodes;
Run a query against the TPCH connector:
SELECT * FROM tpch.tiny.region;