[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293466#comment-17293466
]
Aakash Nand edited comment on RANGER-3182 at 3/20/21, 10:13 AM:
----------------------------------------------------------------
I have recently built ranger from tag 2.1.0 and created a patch for migration
of prestosql to trino. as [~inpt333] mentioned I faced the problem with JDK11
so I had to use one more patch for JDK11. I am attaching both patches here for
your reference. The JDK11 patch was from
https://issues.apache.org/jira/browse/RANGER-2317 issue. More refactoring might
be required. The file trino.patch attached here already contains jdk11.patch.
If someone can guide me, I would like to take this issue
[^jdk11.patch]
was (Author: aakashnand):
I have recently built ranger from tag 2.1.0 and created a patch for migration
of prestosql to trino. as [~inpt333] mentioned I faced the problem with JDK11
so I had to use one more patch for JDK11. I am attaching both patches here for
your reference. The JDK11 patch was from
https://issues.apache.org/jira/browse/RANGER-2317 issue. More refactoring might
be required. The file trino.patch attached here already contains jdk11.patch.
If someone can guide me, I would like to take this issue
[^trino.patch]
[^jdk11.patch]
> 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: jdk11.patch, trino.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)
