Trino

Trino is a fast distributed SQL query engine for big data analytics. See DEVELOPMENT for information about development and release process, code style and guidelines for implementors of Trino plugins. Trino is a standard Maven project. Simply run the following command from the project root directory: 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. The simplest way to run Trino for development is to run the TpchQueryRunner 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. The VM option generally required here is --add-modules jdk.incubator.vector , but various QueryRunner classes might require additional options (if necessary, check the air.test.jvm.additional-arguments property in the pom.xml file of the module from which the runner comes). When running individual test classes directly from IntelliJ, you need to configure the JUnit run configuration template. Go to Run/Debug Configurations Edit Configuration Templates JUnit VM options and set the value to -ea --add-modules=jdk.incubator.vector . Some tests may rely on JVM options provided by airbase (e.g. -XX:-OmitStackTraceInFastThrow ), so check for that too. Trino comes with sample configuration that should work out-of-the-box for development. Use the following options to create a run configuration: The working directory should be the trino-server-dev subdirectory. In IntelliJ, using $MODULE DIR$ accomplishes this automatically.