[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534727#comment-17534727
]
Ramesh Mani commented on RANGER-3182:
-------------------------------------
[~aakashnand] Even I didn't want to miss out this chance of getting Trino
Plugin into Apache Ranger release, that is why I was keen on reviewing and
having it ready for this release 2.3 of Ranger.
I have created the following Jira to activate the trino plugin build only with
JDK11. But this needs testing from your side that Plugin Trino is building
properly in JDK 11 and artifacts that are need are created. Could you please
help me with it?
https://issues.apache.org/jira/browse/RANGER-3755
Review Request for Ranger-3755:[https://reviews.apache.org/r/73984/]
> 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)
