[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527772#comment-17527772 ]
Matthew Sharp commented on RANGER-3182: --------------------------------------- We recently back ported the patches for the Trino plugin in a new 2.1 build and I wanted to call out that leaving the Trino service definition ID at 17 will break existing installations when they try to upgrade. Presto already exists in the x_service_def table with that ID for anyone that is running Ranger today, so you need to move this to a new ID. https://github.com/apache/ranger/pull/120/files#diff-01520b24d11bcc56a0bf7a64f9046da412027a4fc6c231f75b2ec21e6e81bafbR2 > Prestosql is renamed to Trino > ----------------------------- > > Key: RANGER-3182 > URL: https://issues.apache.org/jira/browse/RANGER-3182 > Project: Ranger > Issue Type: Improvement > Components: plugins > Affects Versions: 2.1.0 > Reporter: Viacheslav Kriuchkov > Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > Remaining Estimate: 0h > > All "prestosql" classes are "trino" now and Presto plugin can't integrate > with Trino because of that. It means all Presto deployments that use Ranger > are stuck on version 350 and can't upgrade further. -- This message was sent by Atlassian Jira (v8.20.7#820007)