Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.env for Trino #472

Open
Va1-ha11a opened this issue Aug 10, 2022 · 2 comments
Open

.env for Trino #472

Va1-ha11a opened this issue Aug 10, 2022 · 2 comments

Comments

@Va1-ha11a
Copy link

The example-env file in still refers to presto:

#MODULES=presto,athena,prod,bq
MODULES=presto

MODULES_PRESTO_ENGINE=presto
MODULES_PRESTO_API=http://presto:8080/v1
MODULES_PRESTO_CATALOG=system
MODULES_PRESTO_SCHEMA=runtime
MODULES_PRESTO_SOURCE=quix
MODULES_PRESTO_DB_EMPTY_TIMEOUT=60000
MODULES_PRESTO_DB_REQUEST_TIMEOUT=10000
`MODULES_PRESTO_HTTP_HEADERS_PREFIX=X-PRESTO-

I have both Trino and Quix installed in docker containers and want to set up the connection. How can I update the code since Presto had been rebranded to Trino?

@antonpodolsky
Copy link
Collaborator

  • Change MODULES_PRESTO_* to MODULES_TRINO_*
  • Change MODULES=presto to MODULES=trino

@antonpodolsky
Copy link
Collaborator

This doesn't really change anything in terms of actual Trino setup, it's just how we manage module naming and configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants