[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311823#comment-17311823
]
Erik Anderson edited comment on RANGER-3182 at 3/30/21, 9:32 PM:
-----------------------------------------------------------------
[~aakashnand] I have a new Ranger 2.1.1 with both a presto and a trino plugin.
I propose a new Ranger 2.1.1 version where we add the trino but for Ranger 3,0
and up we remove the presto.
A new plugin is a requirement because just renaming Presto to Trino caused the
GUID to be reused. This will cause issues for people upgrading.
I also ran into the same problems building the ranger-distro-example. I am
unsure why any default build would include examples? That just doesnt make
sense. ranger-examples should be removed from the default build. Examples
should be independent Ranger itself.
was (Author: erikanderson):
[~aakashnand] I have a new Ranger 2.1.1 with both a presto and a trino plugin.
I propose a new Ranger 2.1.1 version where we add the trino but for Ranger 3,0
and up we remove the presto.
I also ran into the same problems building the ranger-distro-example. I am
unsure why any default build would include examples? That just doesnt make
sense. ranger-examples should be removed from the default build. Examples
should be independent Ranger itself.
> 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)
