[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290936#comment-17290936
]
Ivan Peña commented on RANGER-3182:
-----------------------------------
[~pradeep] I prepared a first draft for the patch here:
[https://github.com/inpt333/ranger/commit/a68d0c55a4c733a5c202b311055078ec0185e9d9]
Not only the migration from PrestoSQL to Trino is required, but also the
upgrade from Java 1.8 to 11 since Trino is using this last one.
I couldn't test it properly yet in our environment though, that's why I didn't
create a PR, but maybe it can already give you more or less an idea of the
effort that it would require to do the migration in a more complete and proper
way.
> 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
> Assignee: Pradeep Agrawal
> Priority: Blocker
>
> 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.3.4#803005)
