[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524135#comment-17524135
]
Aakash Nand commented on RANGER-3182:
-------------------------------------
[~rmani]
Yes, you are correct. When users want to migrate from Ranger 2.2.0 to Ranger
2.3.0, they would need to migrate existing policies to be imported to the Trino
service.
Also some refactoring might be required. Such as changing JDBC name from
`io.prestosql.jdbc.PrestoDriver` to `io.trino.jdbc.TrinoDriver`
We can share this guide from Trino Documentation as well
[https://trino.io/blog/2021/01/04/migrating-from-prestosql-to-trino.html]
I have created a Review request. Let me know if some additional testing should
be done
https://reviews.apache.org/r/73643/
> 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.1#820001)
