io.prestosql:presto-resource-group-managers

Presto - Resource Group Configuration Managers

License

License

GroupId

GroupId

io.prestosql
ArtifactId

ArtifactId

presto-resource-group-managers
Last Version

Last Version

350
Release Date

Release Date

Type

Type

presto-plugin
Description

Description

Presto - Resource Group Configuration Managers

Download presto-resource-group-managers

Dependencies

compile (20)

Group / Artifact Type Version
io.prestosql : presto-plugin-toolkit jar 350
io.airlift : bootstrap jar 202
io.airlift : concurrent jar 202
io.airlift : configuration jar 202
io.airlift : json jar 202
io.airlift : log jar 202
io.airlift : stats jar 202
io.airlift : units jar 1.6
com.fasterxml.jackson.core : jackson-core jar 2.11.1
com.fasterxml.jackson.core : jackson-databind jar 2.11.1
com.google.code.findbugs : jsr305 Optional jar 3.0.2
com.google.guava : guava jar 29.0-jre
com.google.inject : guice jar 4.2.3
javax.annotation : javax.annotation-api jar 1.3.2
javax.inject : javax.inject jar 1
javax.validation : validation-api jar 2.0.1.Final
mysql : mysql-connector-java jar 5.1.48
org.jdbi : jdbi3-core jar 3.17.0
org.jdbi : jdbi3-sqlobject jar 3.17.0
org.weakref : jmxutils jar 1.21

provided (4)

Group / Artifact Type Version
io.prestosql : presto-spi jar 350
io.airlift : slice jar 0.39
com.fasterxml.jackson.core : jackson-annotations jar 2.11.1
org.openjdk.jol : jol-core jar 0.2

test (5)

Group / Artifact Type Version
io.prestosql : presto-main jar 350
io.airlift : testing jar 202
com.h2database : h2 jar 1.4.200
org.assertj : assertj-core jar 3.14.0
org.testng : testng jar 6.10

Project Modules

There are no modules declared in this project.

Trino Logo

Trino is a fast distributed SQL query engine for big data analytics.

See the User Manual for deployment instructions and end user documentation.

Trino download Trino Slack Presto: The Definitive Guide book download

Development

See DEVELOPMENT for information about code style, development process, and guidelines.

See CONTRIBUTING for contribution requirements.

Build requirements

  • Mac OS X or Linux
  • Java 11.0.7+, 64-bit
  • Docker

Building Trino

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.

Running Trino in your IDE

Overview

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 pom.xml file.

After opening the project in IntelliJ, double check that the Java SDK is properly configured for the project:

  • Open the File menu and select Project Structure
  • In the SDKs section, ensure that JDK 11 is selected (create one if none exist)
  • In the Project section, ensure the Project language level is set to 11

Running a testing server

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.

Running the full server

Trino comes with sample configuration that should work out-of-the-box for development. Use the following options to create a run configuration:

  • Main Class: io.trino.server.TrinoServer
  • VM Options: -ea -Dconfig=etc/config.properties -Dlog.levels-file=etc/log.properties -Djdk.attach.allowAttachSelf=true
  • Working directory: $MODULE_DIR$
  • Use classpath of module: trino-server-main

The working directory should be the trino-server-main subdirectory. In IntelliJ, using $MODULE_DIR$ accomplishes this automatically.

Running the CLI

Start the CLI to connect to the server and run SQL queries:

client/trino-cli/target/trino-cli-*-executable.jar

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;
io.prestosql
We have moved to https://github.com/trinodb

Versions

Version
350
349
348
347
346
345
344
343
342
341
340
339
338
337
336
335
334
333
332
331
330
329
328
327
326
325
324
323
322
321
320
319
318
317
316
315
314
313
312
311
310
309
308
307
306
305
304
303
302
301
300