[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524120#comment-17524120
]
Ramesh Mani commented on RANGER-3182:
-------------------------------------
[~aakashnand] Thanks for the patch. One concern I had was how do this change
affect the upgrade. Say from 2.2.0 to 2.3.0 if some one has to upgrade would be
the necessary step that has to be done.
I see Policies maintained against Presto service has to be exported and
imported into Trino Service.
Also please create a review request in [https://reviews.apache.org/]
Cancel the existing one, lets review this before pushing it.
> 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)
