[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308938#comment-17308938
]
Young Chen commented on RANGER-3182:
------------------------------------
Also tried rebuilding with AdoptOpenJDK and it was fine:
{code:java}
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home:
/usr/local/Cellar/maven/3.6.3_1/libexec Java version: 11.0.10, vendor:
AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home Default
locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version:
"10.15.7", arch: "x86_64", family: "mac"
{code}
Actually nevermind I see, I'm building on master which has the
HIVERangerAuthorizerTest set to ignore.
This brings up the question of whether patching Trino support into older
releases makes sense. I feel that it wouldn't be unreasonable for Trino support
to come exclusively in a new release of ranger, as I would kind of expect
previous releases of Ranger to work with previous releases of prestosql.
Then again, I'm pretty new to the community so any guidance here would be
appreciated.
> 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)
