![]() You will also need to change the connection scheme from “jdbc:presto” to “jdbc:trino”. As you pointed out, we rebranded so if you are connecting to a Trino server version >= 351, you need to make sure you’re using a Trino jdbc client >= 351 as the namespace has changed. I’d like to make a few additional comments regarding the setup for Trino. Let me know if you have any comments or feedback. Presto in particular is one that is especially powerful. IntelliJ's database explorer is slick and integrated experience and you can easily use any JDBC Driver. If you don't like this, then have a look at DBeaver which supports PrestoDB and PrestoSQL without downloading the driver. Small price to pay, or we can all keep voting for this feature and maybe someday IntelliJ will add it. Since IntelliJ isn't managing the driver, you'll be responsible for your own updates. If presto is missing or has catalog access restrictions, you may not be able to see or query all of the datasources and schemas that presto is attached to. On the other hand if presto is secured with file based store or LDAP you'll need to be granted credentials. You may also have basic networking issues, so test if you can even connect to the host/port (maybe through the ui if permitted by your systems team).īy default presto doesn't require credentials, so even though it shows username and password, you might be able to just put in "presto" and either blank or some garbage into password. By default, presto runs on 8080 but if your team set it up with ssl 443 might be the right setup, or it could even be a custom port. Make sure the protocols, address, and ports are correct. On the way, there could be a few "gotchas" so here's a quick list of things that could trip you up. Schema explorer and keyboard completion. ![]() Hopefully this will unlock all the presto possibilities for you! NOTE : make sure to use full url with jdbc protocol and portĮnter fullscreen mode Exit fullscreen mode If you're dealing with particularly large amount of tables, this step could take a while. The last step is particularly helpful if you presto is hosting multiple catalogs across database instances. select "All Databases" and also select "All Schemas".
0 Comments
Leave a Reply. |