[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305396#comment-17305396
]
Aakash Nand commented on RANGER-3182:
-------------------------------------
I have added two patch files, one for the _release-ranger-2.1.0_ and one for
the _master_ branch. This patch also includes the JDK11 compilation patch
RANGER-2317 and a patch to resolve compilation error for JDK11 for
ranger-distro-example from [this GitHub
PR|https://github.com/apache/ranger/pull/71] except for hive-agent. In
hive-agent, there are still references to JDK8 which are blocker to use JDK11
for building ranger. (reference: HIVE-21584 )for ranger but apart from that
this works fine for all other modules. So I used the following command to build
the ranger without a hive-agent module. This will create trino-plugin.tar.gz in
the target folder along with other modules.
{noformat}
mvn clean compile package assembly:assembly install -pl '!hive-agent'{noformat}
The system I used for the build was
OS: Ubuntu18:04
Java 11
Maven version output
{noformat}
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/apache-maven-3.6.3
Java version: 11.0.7, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-45-generic", arch: "amd64", family:
"unix"{noformat}
> 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
>
>
> 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)
