Hi, I'm Antonio Romero, from the product management team behind Starburst Presto.
Pulsar has recently come on my radar, and I'm aware that at some point in the relatively recent past the Pulsar project switched to using PrestoSQL from PrestoDB as the basis for your SQL query functionality. Some of you are no doubt aware that PrestoSQL was recently renamed Trino because of trademark issues over the name Presto. This has meant renaming a bunch of objects in the Trino code, and getting those who build integrations around our SPI to update their code accordingly. The guidelines on updating existing code to run with Trino are here: https://docs.starburst.io/latest/appendix/to-sep-354-plus.html#custom-plugins-using-the-spi If you have any custom plugins for SEP, such as connectors or functions, these must be updated by changing the source code of your plugin to adapt to the new SPI. All changes are an easy refactor with an IDE. The package name is now io.trino.spi, and a few classes are renamed: PrestoException to TrinoException PrestoPrincipal to TrinoPrincipal PrestoWarning to TrinoWarning There are no functional changes, so you only need to perform the following steps: - Update all import statements. - Rename the references to the above class names. - Rebuild your plugin into a new binary. - Replace the old plugin in your deployment with the updated binary. If I can do anything to help you with the transition, please contact by email and I will see what I can arrange. Thanks for your time, -Antonio Romero Product Manager, Starburst Data
