[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534753#comment-17534753
]
Aakash Nand commented on RANGER-3182:
-------------------------------------
Ohh I think I got it.
Using activation means if we use JDK11 then the trino plugin will be activated
in build and if we use jdk8 it will be deactivated hence there will be no error
while building. Is my understanding correct? If this works, Is there any chance
we could still include this in the Ranger2.3 release?
> 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: Ramesh Mani
> Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino-master.patch,
> 0001-RANGER-3182-Rename-Prestosql-to-Trino-ranger-2.3.patch,
> ranger-commons-lang3-master.patch
>
> Time Spent: 2h 50m
> 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.7#820007)
