![]() Last thing is that if you have enabled SSL/TLS on your Trino (or Presto) cluster, you will need to add SSL=true to the parameter list of your jdbc connection string. We realize this adds a bit more confusion to the article but as you read in the Trino rebrand blog, our hands were forced as Facebook and the Linux Foundation enforced the Presto trademark. 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". Right click on new Datasource->Database Tools->Manage Shown Schemas.Add the Datasource and use the Driver (and click "Test connection".).Pick the driver class (facebook or prestosql).Under the "Driver Files" box, click the and browse to the downloaded jdbc jar.Enter "PrestoSQL" or "PrestoDB" in the name (whichever driver you chose.In "Database" panel click or right click and select New -> "Driver".~/Library/Application\ Support/JetBrains/IntelliJIdea2020.2/jdbc-drivers/ So just click the link under "JDBC Driver" and download it. Trino, the rename of the fork PrestoSQL the fork of the project in the community PrestoDB, the original project by Facebook. I encourage folks to follow their releases for more critical information. Not surprisingly there is a JDBC driver for each and mostly they seem to be nearly identical, however at the time of writing, PrestoSQL's driver performed a bit faster for me. If you don't know by now, there's two forks of presto in the universe. While it's not totally un-intuitive, many people trying to set it up might not see the options and give up. If you like ancient history, feel free to keep reading :) Happy coding! UPDATE - IntelliJ and DataGrip now have drivers for presto and trino right out of the oven, so no need to read on! So it should be totally well documented how to set it up with IntelliJ, right? Not so fast. Presto is a cool technology that works with everything (within reason).
0 Comments
Leave a Reply. |