[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310969#comment-17310969
]
Young Chen commented on RANGER-3182:
------------------------------------
Sounds good, thanks Aakash!
On another note, I'm trying to install ranger from the branch you've shared.
There are two issues I ran into:
# commons-lang3 and commons-compress are missing from the installer and
commons-lang3 is missing from the plugin once installed. (Running into no class
found exceptions during these steps). I updated the assembly xml and a pom to
fix it: [^ranger-commons-lang3-master.patch]
# This change doesn't work with pre existing ranger installations. Seems like
since the ranger servicedef tables are already bootstrapped, the trino service
doesn't get added to the admin webapp, and the Presto service stays available
(but no longer has a valid ranger service class backing it).
Have you run into 1. as well? Or is there something wrong with my setup?
Also, it seems like your new approach to keep prestosql and add trino would
address 2.
> 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
> Attachments: 0001-RANGER-3182-Rename-Presto-to-Trino-2.1.0.patch,
> 0001-RANGER-3182-Rename-Presto-to-Trino-3.0.0-master.patch,
> ranger-commons-lang3-master.patch
>
>
> 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)
