[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293466#comment-17293466 ] Aakash Nand commented on RANGER-3182: - 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. [^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)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ 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/2/21, 7:47 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 tell me how do I contribute, I would like to take this issue [^trino.patch] [^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. [^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)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ 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/2/21, 7:53 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 [^trino.patch] [^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 tell me how do I contribute, 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)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ 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 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 [^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 > > 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)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 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 > > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: trino.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 > > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Presto-to-Trino-2.1.0.patch 0001-RANGER-3182-Rename-Presto-to-Trino-3.0.0-master.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: 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[
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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Presto-to-Trino-2.1.0.patch 0001-RANGER-3182-Rename-Presto-to-Trino-3.0.0-master.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: 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Presto-to-Trino-3.0.0-master.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: 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Presto-to-Trino-2.1.0.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: 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Presto-to-Trino-2.1.0.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: 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Presto-to-Trino-2.1.0.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: 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308281#comment-17308281
]
Aakash Nand commented on RANGER-3182:
-
[~youchen] Thank you for the feedback. What version of JDK are you using to
build the ranger also which version of a ranger are you building? I am using
the following maven and JDK version and ranger branch for 2.1.0
{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}
and while building hive-agent I am getting the following error in the test case.
{noformat}
[ERROR] org.apache.ranger.services.hive.HIVERangerAuthorizerTest Time elapsed:
0.984 s <<< ERROR! java.lang.RuntimeException: Error applying authorization
policy on hive configuration: class
jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to class
java.net.URLClassLoader (jdk.internal.loader.ClassLoaders$AppClassLoader and
java.net.URLClassLoader are in module java.base of loader 'bootstrap') at
org.apache.ranger.services.hive.HIVERangerAuthorizerTest.setup(HIVERangerAuthorizerTest.java:99)
Caused by: java.lang.ClassCastException: class
jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to class
java.net.URLClassLoader (jdk.internal.loader.ClassLoaders$AppClassLoader and
java.net.URLClassLoader are in module java.base of loader 'bootstrap') at
org.apache.ranger.services.hive.HIVERangerAuthorizerTest.setup(HIVERangerAuthorizerTest.java:99)
{noformat}
_class jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to class
java.net.URLClassLoader_
is the big hint. I believe hive using JDK8 and I am using JDK11 for building.
This error is similar to this ticket
https://issues.apache.org/jira/browse/HIVE-21584.
> 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310687#comment-17310687 ] Aakash Nand commented on RANGER-3182: - [~youchen] yes, you are right, in the current patch I have completely removed the prestosql plugin and added trino but the better way is to keep the presto plugin as it is and add the trino-plugin additionally. I am working on it and will update the patches soon. > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Presto-to-Trino-3.0.0-master.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 >Priority: Blocker > Attachments: ranger-commons-lang3-master.patch > > Time Spent: 40m > 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.3.4#803005)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Presto-to-Trino-2.1.0.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 >Priority: Blocker > Attachments: ranger-commons-lang3-master.patch > > Time Spent: 40m > 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.3.4#803005)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Prestosql-to-Trino.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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 40m > 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.3.4#803005)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426952#comment-17426952 ] Aakash Nand commented on RANGER-3182: - I have submitted a review request here. Please review https://reviews.apache.org/r/73643/ > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 40m > 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.3.4#803005)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513756#comment-17513756 ] Aakash Nand commented on RANGER-3182: - Here is the article that I wrote for Ranger Trino Integration [Integrating-Trino-and-Apache-Ranger|https://towardsdatascience.com/integrating-trino-and-apache-ranger-b808f6b96ad8] > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523021#comment-17523021 ] Aakash Nand commented on RANGER-3182: - [~rmani] which branch should I use for rebasing? Is cdpd-master branch correct? > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523036#comment-17523036 ] Aakash Nand commented on RANGER-3182: - [~rmani] Understood. Please allow me sometime, I will rebase and send updated 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523036#comment-17523036 ] Aakash Nand edited comment on RANGER-3182 at 4/16/22 7:44 AM: -- [~rmani] Understood. Please allow me sometime, I will rebase and send updated patch. I could not find the cdpd-master branch though was (Author: aakashnand): [~rmani] Understood. Please allow me sometime, I will rebase and send updated 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Prestosql-to-Trino.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 >Priority: Blocker > Attachments: ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Prestosql-to-Trino.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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523984#comment-17523984 ] Aakash Nand commented on RANGER-3182: - [~rmani], I have attached a new patch file. It contains all the changes and it also works on the master branch. Please check. I also ensured that all the builds and tests are successful. > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523984#comment-17523984
]
Aakash Nand edited comment on RANGER-3182 at 4/19/22 2:19 AM:
--
[~rmani], I have attached a new patch file. It contains all the changes and it
also works on the master branch. Please check. I also ensured that all the
builds and tests are successful. The local environment that I used was
{{{}Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f){}}}{{{}Maven
home: /opt/apache-maven-3.6.3{}}}{{{}Java version: 11.0.14.1, vendor: Homebrew,
runtime:
/usr/local/Cellar/openjdk@11/11.0.14.1/libexec/openjdk.jdk/Contents/Home{}}}{{{}Default
locale: en_JP, platform encoding: UTF-8{}}}{{{}OS name: "mac os x", version:
"12.3", arch: "x86_64", family: "mac"{}}}
was (Author: aakashnand):
[~rmani], I have attached a new patch file. It contains all the changes and it
also works on the master branch. Please check. I also ensured that all the
builds and tests are successful.
> 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
>Priority: Blocker
> Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch,
> ranger-commons-lang3-master.patch
>
> Time Spent: 2h 40m
> 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.1#820001)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523984#comment-17523984
]
Aakash Nand edited comment on RANGER-3182 at 4/19/22 3:31 AM:
--
[~rmani], I have attached a new patch file. It contains all the changes and it
also works on the master branch. Please check. I also ensured that all the
builds and tests are successful.
The local environment that I used was
{code:java}
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)Maven home:
/opt/apache-maven-3.6.3Java version: 11.0.14.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@11/11.0.14.1/libexec/openjdk.jdk/Contents/HomeDefault
locale: en_JP, platform encoding: UTF-8OS name: "mac os x", version: "12.3",
arch: "x86_64", family: "mac"{code}
For master branch use
{code:java}
git am < 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch{code}
For the ranger-2.3 branch use{{{}{}}}
{code:java}
git am --3way --ignore-space-change
../0001-RANGER-3182-Rename-Prestosql-to-Trino.patch
{code}
was (Author: aakashnand):
[~rmani], I have attached a new patch file. It contains all the changes and it
also works on the master branch. Please check. I also ensured that all the
builds and tests are successful. The local environment that I used was
{{{}Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f){}}}{{{}Maven
home: /opt/apache-maven-3.6.3{}}}{{{}Java version: 11.0.14.1, vendor: Homebrew,
runtime:
/usr/local/Cellar/openjdk@11/11.0.14.1/libexec/openjdk.jdk/Contents/Home{}}}{{{}Default
locale: en_JP, platform encoding: UTF-8{}}}{{{}OS name: "mac os x", version:
"12.3", arch: "x86_64", family: "mac"{}}}
> 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
>Priority: Blocker
> Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch,
> ranger-commons-lang3-master.patch
>
> Time Spent: 2h 40m
> 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.1#820001)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523984#comment-17523984
]
Aakash Nand edited comment on RANGER-3182 at 4/19/22 3:32 AM:
--
[~rmani], I have attached a new patch file. It contains all the changes and it
also works on the master branch. Please check. I also ensured that all the
builds and tests are successful.
The local environment that I used was
{code:java}
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)Maven home:
/opt/apache-maven-3.6.3Java version: 11.0.14.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@11/11.0.14.1/libexec/openjdk.jdk/Contents/HomeDefault
locale: en_JP, platform encoding: UTF-8OS name: "mac os x", version: "12.3",
arch: "x86_64", family: "mac"{code}
For applying the patch to the master branch use ↓
{code:java}
git am < 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch{code}
For applying the patch to the ranger-2.3 branch use ↓
{code:java}
git am --3way --ignore-space-change
../0001-RANGER-3182-Rename-Prestosql-to-Trino.patch
{code}
was (Author: aakashnand):
[~rmani], I have attached a new patch file. It contains all the changes and it
also works on the master branch. Please check. I also ensured that all the
builds and tests are successful.
The local environment that I used was
{code:java}
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)Maven home:
/opt/apache-maven-3.6.3Java version: 11.0.14.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@11/11.0.14.1/libexec/openjdk.jdk/Contents/HomeDefault
locale: en_JP, platform encoding: UTF-8OS name: "mac os x", version: "12.3",
arch: "x86_64", family: "mac"{code}
For master branch use
{code:java}
git am < 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch{code}
For the ranger-2.3 branch use{{{}{}}}
{code:java}
git am --3way --ignore-space-change
../0001-RANGER-3182-Rename-Prestosql-to-Trino.patch
{code}
> 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
>Priority: Blocker
> Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch,
> ranger-commons-lang3-master.patch
>
> Time Spent: 2h 40m
> 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.1#820001)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524135#comment-17524135 ] Aakash Nand commented on RANGER-3182: - [~rmani] Yes, you are correct. When users want to migrate from Ranger 2.2.0 to Ranger 2.3.0, they would need to migrate existing policies to be imported to the Trino service. Also some refactoring might be required. Such as changing JDBC name from `io.prestosql.jdbc.PrestoDriver` to `io.trino.jdbc.TrinoDriver` We can share this guide from Trino Documentation as well [https://trino.io/blog/2021/01/04/migrating-from-prestosql-to-trino.html] I have created a Review request. Let me know if some additional testing should be done https://reviews.apache.org/r/73643/ > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524135#comment-17524135 ] Aakash Nand edited comment on RANGER-3182 at 4/19/22 7:23 AM: -- [~rmani] Yes, you are correct. When users want to migrate from Ranger 2.2.0 to Ranger 2.3.0, they would need to migrate existing policies to be imported to the Trino service. Also some refactoring might be required. Such as changing JDBC name from `io.prestosql.jdbc.PrestoDriver` to `io.trino.jdbc.TrinoDriver` We can share this guide from Trino Documentation which explains how to have background compatibility [https://trino.io/blog/2021/01/04/migrating-from-prestosql-to-trino.html] I have created a Review request. Let me know if some additional testing should be done [https://reviews.apache.org/r/73643/] was (Author: aakashnand): [~rmani] Yes, you are correct. When users want to migrate from Ranger 2.2.0 to Ranger 2.3.0, they would need to migrate existing policies to be imported to the Trino service. Also some refactoring might be required. Such as changing JDBC name from `io.prestosql.jdbc.PrestoDriver` to `io.trino.jdbc.TrinoDriver` We can share this guide from Trino Documentation as well [https://trino.io/blog/2021/01/04/migrating-from-prestosql-to-trino.html] I have created a Review request. Let me know if some additional testing should be done https://reviews.apache.org/r/73643/ > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524135#comment-17524135 ] Aakash Nand edited comment on RANGER-3182 at 4/19/22 7:37 AM: -- [~rmani] Yes, you are correct. When users want to migrate from Ranger 2.2.0 to Ranger 2.3.0, they would need to migrate existing policies to be imported to the Trino service. Also some refactoring might be required. Such as changing JDBC name from `io.prestosql.jdbc.PrestoDriver` to `io.trino.jdbc.TrinoDriver` We can share this guide from Trino Documentation which explains how to have background compatibility [https://trino.io/blog/2021/01/04/migrating-from-prestosql-to-trino.html] I have created a Review request. Let me know if some additional testing should be done https://reviews.apache.org/r/73948/ was (Author: aakashnand): [~rmani] Yes, you are correct. When users want to migrate from Ranger 2.2.0 to Ranger 2.3.0, they would need to migrate existing policies to be imported to the Trino service. Also some refactoring might be required. Such as changing JDBC name from `io.prestosql.jdbc.PrestoDriver` to `io.trino.jdbc.TrinoDriver` We can share this guide from Trino Documentation which explains how to have background compatibility [https://trino.io/blog/2021/01/04/migrating-from-prestosql-to-trino.html] I have created a Review request. Let me know if some additional testing should be done [https://reviews.apache.org/r/73643/] > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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.1#820001)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527821#comment-17527821 ] Aakash Nand commented on RANGER-3182: - [~rmani], I added some comments in the review request. Also, what do you think of [~MatthewSharp]'s suggestion? Should we change the service definition ID from 17 to some other number like 18 or something? > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Prestosql-to-Trino.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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Prestosql-to-Trino.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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529287#comment-17529287 ] Aakash Nand commented on RANGER-3182: - [~rmani], I have fixed almost all the issues from the review request. Please check the only remaining issue in the review request. Once that is solved I think we are good to go. > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529287#comment-17529287 ] Aakash Nand edited comment on RANGER-3182 at 4/28/22 8:11 AM: -- [~rmani], I have fixed almost all the issues from the review request and have attached the latest patch in the review request as well as this issue. Please check the only remaining issue in the review request. Once that is solved I think we are good to go. was (Author: aakashnand): [~rmani], I have fixed almost all the issues from the review request. Please check the only remaining issue in the review request. Once that is solved I think we are good to go. > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532530#comment-17532530 ] Aakash Nand commented on RANGER-3182: - [~rmani] I am going to upload the new patch in the review by end of the day today, please review it again. > 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 >Priority: Blocker > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, > ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Prestosql-to-Trino.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 >Priority: Blocker > Attachments: ranger-commons-lang3-master.patch > > Time Spent: 2h 40m > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Prestosql-to-Trino-master.patch 0001-RANGER-3182-Rename-Prestosql-to-Trino-ranger-2.3.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 >Priority: Blocker > 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 40m > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532786#comment-17532786 ] Aakash Nand commented on RANGER-3182: - [~rmani] I have updated the patch files in the review link as well as this issue. Please review them. > 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 >Priority: Blocker > 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 40m > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533412#comment-17533412 ] Aakash Nand commented on RANGER-3182: - [~rmani] Working on it. Will update it soon. > 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 >Priority: Blocker > 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 40m > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: 0001-RANGER-3182-Rename-Prestosql-to-Trino-ranger-2.3.patch 0001-RANGER-3182-Rename-Prestosql-to-Trino-master.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 >Priority: Blocker > 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 40m > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Prestosql-to-Trino-ranger-2.3.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 >Priority: Blocker > 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 40m > 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)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3182: Attachment: (was: 0001-RANGER-3182-Rename-Prestosql-to-Trino-master.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 >Priority: Blocker > 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 40m > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533426#comment-17533426 ] Aakash Nand commented on RANGER-3182: - [~rmani], I have deleted the file. Sorry for the delay and thank you for helping throughout the review. > 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 >Priority: Blocker > 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 40m > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533601#comment-17533601 ] Aakash Nand commented on RANGER-3182: - [~rmani], Thank you. I am not able to close this ticket, I may not have permissions > 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 >Priority: Blocker > Fix For: 3.0.0, 2.3.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 40m > 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)
[jira] [Created] (RANGER-3751) ElasticSearch Audit shows wrong date on Ranger-admin UI
Aakash Nand created RANGER-3751:
---
Summary: ElasticSearch Audit shows wrong date on Ranger-admin UI
Key: RANGER-3751
URL: https://issues.apache.org/jira/browse/RANGER-3751
Project: Ranger
Issue Type: Bug
Components: admin, audit
Affects Versions: 3.0.0, 2.3.0
Reporter: Aakash Nand
Recently AmazonCloudWatch support was added to the audit module in this commit.
However, this commit also changed the _toDate_ method of
_ElasticSearchAccessAuditsService.java_ because of which the event time on the
Audit screen is showing the wrong date from 1970. The error stack is as follows:
{noformat}
2022-05-08 07:04:22,887 [http-nio-6080-exec-6] ERROR [MiscUtil.java:938] Error
converting value to date. Value = 2022-05-08T06:42:01.621Z
java.lang.IllegalArgumentException: null
at java.base/java.util.Date.parse(Date.java:616)
at java.base/java.util.Date.(Date.java:274)
at org.apache.ranger.audit.provider.MiscUtil.toDate(MiscUtil.java:936)
at
org.apache.ranger.elasticsearch.ElasticSearchAccessAuditsService.populateViewBean(ElasticSearchAccessAuditsService.java:260)
at
org.apache.ranger.elasticsearch.ElasticSearchAccessAuditsService.searchXAccessAudits(ElasticSearchAccessAuditsService.java:95)
at org.apache.ranger.biz.AssetMgr.getAccessLogs(AssetMgr.java:1139)
at org.apache.ranger.rest.AssetREST.getAccessLogs(AssetREST.java:672)
at
org.apache.ranger.rest.AssetREST$$FastClassBySpringCGLIB$$8cffcb6d.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at
org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:61)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at
org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123){noformat}
The screenshot shows the erroneous date on ranger-admin
Please refer:
https://github.com/apache/ranger/commit/71744d3ff8e0db7f0a49881a891e77edf0ea518d#r73132360
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (RANGER-3751) ElasticSearch Audit shows wrong date on Ranger-admin UI
[
https://issues.apache.org/jira/browse/RANGER-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3751:
Attachment: admin-ui-audit-screen.png
> ElasticSearch Audit shows wrong date on Ranger-admin UI
> ---
>
> Key: RANGER-3751
> URL: https://issues.apache.org/jira/browse/RANGER-3751
> Project: Ranger
> Issue Type: Bug
> Components: admin, audit
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Attachments: admin-ui-audit-screen.png
>
>
> Recently AmazonCloudWatch support was added to the audit module in this
> commit.
> However, this commit also changed the _toDate_ method of
> _ElasticSearchAccessAuditsService.java_ because of which the event time on
> the Audit screen is showing the wrong date from 1970. The error stack is as
> follows:
> {noformat}
> 2022-05-08 07:04:22,887 [http-nio-6080-exec-6] ERROR [MiscUtil.java:938]
> Error converting value to date. Value = 2022-05-08T06:42:01.621Z
> java.lang.IllegalArgumentException: null
> at java.base/java.util.Date.parse(Date.java:616)
> at java.base/java.util.Date.(Date.java:274)
> at org.apache.ranger.audit.provider.MiscUtil.toDate(MiscUtil.java:936)
> at
> org.apache.ranger.elasticsearch.ElasticSearchAccessAuditsService.populateViewBean(ElasticSearchAccessAuditsService.java:260)
> at
> org.apache.ranger.elasticsearch.ElasticSearchAccessAuditsService.searchXAccessAudits(ElasticSearchAccessAuditsService.java:95)
> at org.apache.ranger.biz.AssetMgr.getAccessLogs(AssetMgr.java:1139)
> at org.apache.ranger.rest.AssetREST.getAccessLogs(AssetREST.java:672)
> at
> org.apache.ranger.rest.AssetREST$$FastClassBySpringCGLIB$$8cffcb6d.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
> at
> org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:61)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123){noformat}
>
>
> The screenshot shows the erroneous date on ranger-admin
>
> Please refer:
> https://github.com/apache/ranger/commit/71744d3ff8e0db7f0a49881a891e77edf0ea518d#r73132360
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533613#comment-17533613 ] Aakash Nand commented on RANGER-3182: - [~bpatel] Can you share the maven command you used? > 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 >Priority: Blocker > Fix For: 3.0.0, 2.3.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)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533613#comment-17533613 ] Aakash Nand edited comment on RANGER-3182 at 5/9/22 5:17 AM: - [~bpatel] Can you share the maven command you used and branch? was (Author: aakashnand): [~bpatel] Can you share the maven command you used? > 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 >Priority: Blocker > Fix For: 3.0.0, 2.3.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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533615#comment-17533615 ] Aakash Nand commented on RANGER-3182: - Got it, Let me confirm, I will post update here again > 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 >Priority: Blocker > Fix For: 3.0.0, 2.3.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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533626#comment-17533626
]
Aakash Nand commented on RANGER-3182:
-
[~bpatel] I just confirmed in my case it is working fine. All modules have
passed the build
{noformat}
[INFO] ranger . SUCCESS [ 10.010 s]
[INFO] Jdbc SQL Connector . SUCCESS [ 9.854 s]
[INFO] Credential Support . SUCCESS [ 14.216 s]
[INFO] Audit Component SUCCESS [ 20.571 s]
[INFO] ranger-plugin-classloader .. SUCCESS [ 9.679 s]
[INFO] Common library for Plugins . SUCCESS [01:11 min]
[INFO] ranger-intg SUCCESS [ 20.753 s]
[INFO] Installer Support Component SUCCESS [ 5.017 s]
[INFO] Credential Builder . SUCCESS [ 11.225 s]
[INFO] Embedded Web Server Invoker SUCCESS [ 11.900 s]
[INFO] Key Management Service . SUCCESS [ 40.890 s]
[INFO] HBase Security Plugin Shim . SUCCESS [ 15.131 s]
[INFO] HBase Security Plugin .. SUCCESS [ 31.203 s]
[INFO] Hdfs Security Plugin ... SUCCESS [ 32.051 s]
[INFO] Hive Security Plugin ... SUCCESS [ 36.780 s]
[INFO] Knox Security Plugin Shim .. SUCCESS [ 13.050 s]
[INFO] Knox Security Plugin ... SUCCESS [01:32 min]
[INFO] Storm Security Plugin .. SUCCESS [ 22.349 s]
[INFO] YARN Security Plugin ... SUCCESS [ 10.885 s]
[INFO] Ozone Security Plugin .. SUCCESS [ 12.289 s]
[INFO] Ranger Util SUCCESS [ 13.282 s]
[INFO] Unix Authentication Client . SUCCESS [ 5.774 s]
[INFO] User Group Synchronizer Util ... SUCCESS [ 4.630 s]
[INFO] ranger-authn ... SUCCESS [ 7.106 s]
[INFO] Security Admin Web Application . SUCCESS [07:01 min]
[INFO] KAFKA Security Plugin .. SUCCESS [01:22 min]
[INFO] SOLR Security Plugin ... SUCCESS [ 24.493 s]
[INFO] NiFi Security Plugin ... SUCCESS [ 14.469 s]
[INFO] NiFi Registry Security Plugin .. SUCCESS [ 15.354 s]
[INFO] Presto Security Plugin . SUCCESS [ 17.157 s]
[INFO] Trino Security Plugin .. SUCCESS [ 18.384 s]
[INFO] Kudu Security Plugin ... SUCCESS [ 6.827 s]
[INFO] Unix User Group Synchronizer ... SUCCESS [01:35 min]
[INFO] Ldap Config Check Tool . SUCCESS [ 7.329 s]
[INFO] Unix Authentication Service SUCCESS [ 8.481 s]
[INFO] KMS Security Plugin SUCCESS [ 32.328 s]
[INFO] Tag Synchronizer ... SUCCESS [ 22.376 s]
[INFO] Hdfs Security Plugin Shim .. SUCCESS [ 7.483 s]
[INFO] Hive Security Plugin Shim .. SUCCESS [ 25.227 s]
[INFO] YARN Security Plugin Shim .. SUCCESS [ 6.773 s]
[INFO] OZONE Security Plugin Shim . SUCCESS [ 9.104 s]
[INFO] Storm Security Plugin shim . SUCCESS [ 7.138 s]
[INFO] KAFKA Security Plugin Shim . SUCCESS [ 6.359 s]
[INFO] SOLR Security Plugin Shim .. SUCCESS [ 8.257 s]
[INFO] Atlas Security Plugin Shim . SUCCESS [ 7.391 s]
[INFO] KMS Security Plugin Shim ... SUCCESS [ 8.606 s]
[INFO] Presto Security Plugin Shim SUCCESS [ 8.182 s]
[INFO] Trino Security Plugin Shim . SUCCESS [ 7.007 s]
[INFO] ranger-examples SUCCESS [ 0.335 s]
[INFO] Ranger Examples - Conditions and ContextEnrichers .. SUCCESS [ 12.120 s]
[INFO] Ranger Examples - SampleApp SUCCESS [ 3.598 s]
[INFO] Ranger Examples - Ranger Plugin for SampleApp .. SUCCESS [ 6.406 s]
[INFO] sample-client .. SUCCESS [ 8.200 s]
[INFO] Apache Ranger Examples Distribution SUCCESS [ 5.338 s]
[INFO] Ranger Tools ... SUCCESS [ 16.618 s]
[INFO] Atlas Security Plugin .. SUCCESS [ 10.591 s]
[INFO] SchemaRegistry Security Plugin . SUCCESS [ 26.479 s]
[INFO] Sqoop Security Plugin .. SUCCESS [ 18.581
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534043#comment-17534043 ] Aakash Nand commented on RANGER-3182: - [~madhan] the updated patch is available in the review request, in fact I have attached the patches to this issue as well as review request by branch wise. Let me know if you still want me to attach it again. > 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 >Priority: Blocker > Fix For: 3.0.0, 2.3.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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534140#comment-17534140 ] Aakash Nand commented on RANGER-3182: - [~madhan] Let me retry again. This time I will clone repo the in the new environment and try again. Will update you soon. > 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 >Priority: Blocker > Fix For: 3.0.0, 2.3.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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534214#comment-17534214
]
Aakash Nand commented on RANGER-3182:
-
[~madhan] I tried building again in a different environment and it is working
for me. I am not sure why you are getting that error. Please check the below
environment information I used,
{code:java}
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /home/aakashnand/opt/apache-maven-3.8.1
Java version: 11.0.13, vendor: Oracle Corporation, runtime:
/home/aakashnand/opt/openjdk-11.0.13_8
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-100-generic", arch: "amd64", family: "unix"
{code}
Command used
{code:java}
mvn clean compile package install -P ranger-trino-plugin,'!linux' -am{code}
{code:java}
[INFO] ranger . SUCCESS [ 13.884 s]
[INFO] Credential Support . SUCCESS [ 15.712 s]
[INFO] Audit Component SUCCESS [ 20.878 s]
[INFO] ranger-plugin-classloader .. SUCCESS [ 7.247 s]
[INFO] Common library for Plugins . SUCCESS [ 57.027 s]
[INFO] Installer Support Component SUCCESS [ 5.306 s]
[INFO] Credential Builder . SUCCESS [ 12.259 s]
[INFO] Ranger Util SUCCESS [ 13.222 s]
[INFO] Trino Security Plugin .. SUCCESS [ 18.628 s]
[INFO] Trino Security Plugin Shim . SUCCESS [ 10.845 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 02:55 min
[INFO] Finished at: 2022-05-10T07:58:54Z
[INFO]
{code}
> 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
>Priority: Blocker
> Fix For: 3.0.0, 2.3.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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534380#comment-17534380 ] Aakash Nand commented on RANGER-3182: - [~madhan] [~rmani] Trino plugin requires JDK11+ and I thought from Ranger 2, java11 support is added. How should we proceed with this? > 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 >Priority: Blocker > Fix For: 3.0.0, 2.3.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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534614#comment-17534614 ] Aakash Nand commented on RANGER-3182: - [~rmani] That's really sad. Any idea when Ranger will start using Java11? There are so many trino users who wanted to use the trino-ranger-plugin and for them, I will keep my personal fork as an option to use the plugin and build with JDK11 and will try to maintain on best effort basis. Whenever this issue status changes, let me know again. For anyone looking for alternative resources on this issue: * [https://github.com/aakashnand/ranger] * [https://github.com/aakashnand/trino-ranger-demo] * Tutorial: [Integrating-Trino-Ranger |https://towardsdatascience.com/integrating-trino-and-apache-ranger-b808f6b96ad8] > 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)
[jira] [Comment Edited] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534614#comment-17534614 ] Aakash Nand edited comment on RANGER-3182 at 5/11/22 1:18 AM: -- [~rmani] That's really sad. Any idea when Ranger will start using Java11? Can we make any setting in pom.xml to make only trino-plugin use JDK11 and keep the rest of the plugins to jdk8? There are so many trino users who wanted to use the trino-ranger-plugin and for them, I will keep my personal fork as an option to use the plugin and build with JDK11 and will try to maintain on best effort basis. Whenever this issue status changes, let me know again. For anyone looking for alternative resources on this issue: * [https://github.com/aakashnand/ranger] * [https://github.com/aakashnand/trino-ranger-demo] * Tutorial: [Integrating-Trino-Ranger |https://towardsdatascience.com/integrating-trino-and-apache-ranger-b808f6b96ad8] was (Author: aakashnand): [~rmani] That's really sad. Any idea when Ranger will start using Java11? There are so many trino users who wanted to use the trino-ranger-plugin and for them, I will keep my personal fork as an option to use the plugin and build with JDK11 and will try to maintain on best effort basis. Whenever this issue status changes, let me know again. For anyone looking for alternative resources on this issue: * [https://github.com/aakashnand/ranger] * [https://github.com/aakashnand/trino-ranger-demo] * Tutorial: [Integrating-Trino-Ranger |https://towardsdatascience.com/integrating-trino-and-apache-ranger-b808f6b96ad8] > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534735#comment-17534735 ] Aakash Nand commented on RANGER-3182: - [~rmani] Sure. How should I apply the changes you made (add them mannually?) and try to build and test it on my environment with JDK8? > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534747#comment-17534747 ] Aakash Nand commented on RANGER-3182: - [~rmani] Got it, will do it and let you know. I was wondering how would this solve the problem of building the entire project? What would be the command and JDK version if we want to build the entire project including trino? > 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)
[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino
[ 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)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534755#comment-17534755 ] Aakash Nand commented on RANGER-3755: - [~rmani], I just tried building it on the 2.3 branch but since in the profile ranger-trino-plugin there is no dependency on the distro module, it is not creating the tar file using assembly. If I build the entire project will it create the tar file using the distro module? I see you also have removed Line Number 78 from distro/pom.xml. I think deleting that line may not create the tar file. > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[
https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534760#comment-17534760
]
Aakash Nand commented on RANGER-3755:
-
[~rmani] Tried using
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin {code}
but it is not creating tar file but the plugin build compilation is successful.
How about we add dependency of
{code:java}
distro{code}
to profile ? Will it have any adverse effects?
> Build Plugin-Trino artifacts only with JDK 11
> -
>
> Key: RANGER-3755
> URL: https://issues.apache.org/jira/browse/RANGER-3755
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
>
> Plugin Trino needs jdk 11 and about to compile and build. In order to avoid
> build issue in Apache Ranger when including Plugin Trino, we need to enable a
> profile so that default build of Apache Ranger will use JDK 1.8 and Plugin
> Trino and its artifacts can be build with JDK 11 profile.
> To build Plugin Trino artifacts following command can be executed.
> mvn clean compile package -P ranger-trino-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[
https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534760#comment-17534760
]
Aakash Nand edited comment on RANGER-3755 at 5/11/22 9:43 AM:
--
[~rmani] Tried using
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin {code}
but it is not creating tar file but the plugin build compilation is successful.
How about we add dependency of
{code:java}
distro{code}
to profile ? Will it have any adverse effects?
I have tested this locally and after adding distro it is creating the required
tar file.
Now the only problem is that if we use jdk11 activation only for trino then
when using JDK11, only trino profile is built. How about we create a complete
new jdk11 profile with other modules as well?
was (Author: aakashnand):
[~rmani] Tried using
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin {code}
but it is not creating tar file but the plugin build compilation is successful.
How about we add dependency of
{code:java}
distro{code}
to profile ? Will it have any adverse effects?
> Build Plugin-Trino artifacts only with JDK 11
> -
>
> Key: RANGER-3755
> URL: https://issues.apache.org/jira/browse/RANGER-3755
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
>
> Plugin Trino needs jdk 11 and about to compile and build. In order to avoid
> build issue in Apache Ranger when including Plugin Trino, we need to enable a
> profile so that default build of Apache Ranger will use JDK 1.8 and Plugin
> Trino and its artifacts can be build with JDK 11 profile.
> To build Plugin Trino artifacts following command can be executed.
> mvn clean compile package -P ranger-trino-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[
https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534760#comment-17534760
]
Aakash Nand edited comment on RANGER-3755 at 5/11/22 9:44 AM:
--
[~rmani] Tried using
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin {code}
but it is not creating tar file but the plugin build compilation is successful.
How about we add dependency of
{code:java}
distro{code}
to profile ? Will it have any adverse effects?
I have tested this locally and after adding distro it is creating the required
tar file.
Now the only problem is that if we use jdk11 activation only for trino then
when using JDK11, only trino profile is built. How about we create a complete
new jdk11 profile with other modules as well? Like we have unix profile etc
was (Author: aakashnand):
[~rmani] Tried using
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin {code}
but it is not creating tar file but the plugin build compilation is successful.
How about we add dependency of
{code:java}
distro{code}
to profile ? Will it have any adverse effects?
I have tested this locally and after adding distro it is creating the required
tar file.
Now the only problem is that if we use jdk11 activation only for trino then
when using JDK11, only trino profile is built. How about we create a complete
new jdk11 profile with other modules as well?
> Build Plugin-Trino artifacts only with JDK 11
> -
>
> Key: RANGER-3755
> URL: https://issues.apache.org/jira/browse/RANGER-3755
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
>
> Plugin Trino needs jdk 11 and about to compile and build. In order to avoid
> build issue in Apache Ranger when including Plugin Trino, we need to enable a
> profile so that default build of Apache Ranger will use JDK 1.8 and Plugin
> Trino and its artifacts can be build with JDK 11 profile.
> To build Plugin Trino artifacts following command can be executed.
> mvn clean compile package -P ranger-trino-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[
https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534760#comment-17534760
]
Aakash Nand edited comment on RANGER-3755 at 5/11/22 9:53 AM:
--
[~rmani] Tried using
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin {code}
but it is not creating tar file but the plugin build compilation is successful.
How about we add dependency of
{code:java}
distro{code}
to profile ? Will it have any adverse effects?
I have tested this locally and after adding distro it is creating the required
tar file.
Now the only problem is that if we use jdk11 activation only for trino then
when using JDK11, only trino profile is built.
This will restrict developers who are using JDK11 to build other modules so
How about we create a complete new jdk11 profile with other modules as well?
Like we have unix profile etc
was (Author: aakashnand):
[~rmani] Tried using
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin {code}
but it is not creating tar file but the plugin build compilation is successful.
How about we add dependency of
{code:java}
distro{code}
to profile ? Will it have any adverse effects?
I have tested this locally and after adding distro it is creating the required
tar file.
Now the only problem is that if we use jdk11 activation only for trino then
when using JDK11, only trino profile is built. How about we create a complete
new jdk11 profile with other modules as well? Like we have unix profile etc
> Build Plugin-Trino artifacts only with JDK 11
> -
>
> Key: RANGER-3755
> URL: https://issues.apache.org/jira/browse/RANGER-3755
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
>
> Plugin Trino needs jdk 11 and about to compile and build. In order to avoid
> build issue in Apache Ranger when including Plugin Trino, we need to enable a
> profile so that default build of Apache Ranger will use JDK 1.8 and Plugin
> Trino and its artifacts can be build with JDK 11 profile.
> To build Plugin Trino artifacts following command can be executed.
> mvn clean compile package -P ranger-trino-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17535855#comment-17535855 ] Aakash Nand commented on RANGER-3755: - [~rmani], I have confirmed that now it is working. When using JDK8 it does not build trino but builds all other modules and when using JDK11 it builds trino with other required modules. Although minor change is required. I have added comments in the review request. Please remove the activation from the individual profile because it overrides the ranger-jdk11 profile and creates only the trino tar file. Once changes are made how are we going to proceed, will you apply your patch separately and then apply my trino patch? > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536376#comment-17536376 ] Aakash Nand commented on RANGER-3755: - [~rmani] please give me some time as I am going to build it again and test with actual trino cluster one last time. I will finish this by noon today JST > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536458#comment-17536458 ] Aakash Nand commented on RANGER-3755: - [~rmani], I have performed the final testing on my side and it is working correctly as expected. Good to go > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536458#comment-17536458 ] Aakash Nand edited comment on RANGER-3755 at 5/13/22 6:51 AM: -- [~rmani], I have performed the final testing for this patch RANGER-3755 on my side and it is working correctly as expected. Good to go, however, I found out that when the trino plugin is used with Ranger it is enabling DEBUG logs by default which is flooding the trino server logs. For that part, Since we have reverted the trino patch I was thinking of adding logback.xml to the trino-plugin tar file. Can I still fix this and add to patch RANGER-3182? I will need this weekend to work on that as the last part? What do you think? was (Author: aakashnand): [~rmani], I have performed the final testing on my side and it is working correctly as expected. Good to go > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536458#comment-17536458 ] Aakash Nand edited comment on RANGER-3755 at 5/13/22 6:54 AM: -- [~rmani], I have performed the final testing for this patch RANGER-3755 on my side and it is working correctly as expected. Good to go, however, I found out that when the trino plugin is used with Ranger it is enabling DEBUG logs by default which is flooding the trino server logs. For that part, Since we have reverted the trino patch I was thinking of adding logback.xml to the trino-plugin tar file. Can I still fix this and add to patch RANGER-3182? I will try to fix it asap but I might need this weekend to work on that as the last part? What do you think? Should I fix that? Can we wait till this weekend? was (Author: aakashnand): [~rmani], I have performed the final testing for this patch RANGER-3755 on my side and it is working correctly as expected. Good to go, however, I found out that when the trino plugin is used with Ranger it is enabling DEBUG logs by default which is flooding the trino server logs. For that part, Since we have reverted the trino patch I was thinking of adding logback.xml to the trino-plugin tar file. Can I still fix this and add to patch RANGER-3182? I will need this weekend to work on that as the last part? What do you think? > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (RANGER-3759) Add default logback configuration file for trino plugin
Aakash Nand created RANGER-3759: --- Summary: Add default logback configuration file for trino plugin Key: RANGER-3759 URL: https://issues.apache.org/jira/browse/RANGER-3759 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: 2.1.0 Reporter: Aakash Nand Fix For: 3.0.0, 2.3.0 We have migrated from log4j to logback for plugins but the default log level of logback configuration is set at DEBUG to Console. This produces unnecessarily detailed logs in the trino server log file. To solve this I will add a trino-ranger-plugin-logback.xml file where users can tune the log level for the trino plugin according to their needs. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (RANGER-3760) Make trino plugin configurable for trino environment running in docker
Aakash Nand created RANGER-3760: --- Summary: Make trino plugin configurable for trino environment running in docker Key: RANGER-3760 URL: https://issues.apache.org/jira/browse/RANGER-3760 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: 2.1.0 Reporter: Aakash Nand Fix For: 3.0.0, 2.3.0 Trino uses different plugin directories for server-type installation and docker installation. The plugin directory needs to be configured as /usr/lib/trino/plugin/ranger when running in docker. Lets make this configurable in install.properties using new property INSTALL_ENV=docker If the user configures this property then trino-ranger-plugin will configure the plugin directory to /usr/lib/trino/plugin/ranger otherwise, it will assume that trino is installed using a non-docker environment and use the default plugin directory location -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537311#comment-17537311 ] Aakash Nand commented on RANGER-3755: - [~rmani], I am almost close to finishing the updates for the trino plugin and I have created separate tickets for these issues. I am currently working on creating patches for these respective Jira issues and testing them. I will upload the patches by EoD. The order in which these patches need to be applied is important so I will let you know about this later. > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537311#comment-17537311 ] Aakash Nand edited comment on RANGER-3755 at 5/16/22 3:12 AM: -- [~rmani], I am almost close to finishing the updates for the trino plugin and I have created separate tickets for these issues. I am currently working on creating patches for these respective Jira issues and testing them. I will upload the patches by EoD. The order in which these patches need to be applied is important so I will let you know about this later. Checkout RANGER-3759 RANGER-3760 was (Author: aakashnand): [~rmani], I am almost close to finishing the updates for the trino plugin and I have created separate tickets for these issues. I am currently working on creating patches for these respective Jira issues and testing them. I will upload the patches by EoD. The order in which these patches need to be applied is important so I will let you know about this later. > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3759) Add default logback configuration file for trino plugin
[ https://issues.apache.org/jira/browse/RANGER-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537610#comment-17537610 ] Aakash Nand commented on RANGER-3759: - [~aakashnand] Yes uploading the patch and will create a review request in a few hours. Testing locally now. > Add default logback configuration file for trino plugin > --- > > Key: RANGER-3759 > URL: https://issues.apache.org/jira/browse/RANGER-3759 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > We have migrated from log4j to logback for plugins but the default log level > of logback configuration is set at DEBUG to Console. This produces > unnecessarily detailed logs in the trino server log file. To solve this I > will add a trino-ranger-plugin-logback.xml file where users can tune the log > level for the trino plugin according to their needs. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (RANGER-3759) Add default logback configuration file for trino plugin
[ https://issues.apache.org/jira/browse/RANGER-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3759: Attachment: 0001-RANGER-3759-Add-default-logback-configuration-for-tr.patch > Add default logback configuration file for trino plugin > --- > > Key: RANGER-3759 > URL: https://issues.apache.org/jira/browse/RANGER-3759 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-RANGER-3759-Add-default-logback-configuration-for-tr.patch > > > We have migrated from log4j to logback for plugins but the default log level > of logback configuration is set at DEBUG to Console. This produces > unnecessarily detailed logs in the trino server log file. To solve this I > will add a trino-ranger-plugin-logback.xml file where users can tune the log > level for the trino plugin according to their needs. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3759) Add default logback configuration file for trino plugin
[ https://issues.apache.org/jira/browse/RANGER-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537615#comment-17537615 ] Aakash Nand commented on RANGER-3759: - [~rmani] Uploaded the patch and created a review request. Please check here https://reviews.apache.org/r/73987/ > Add default logback configuration file for trino plugin > --- > > Key: RANGER-3759 > URL: https://issues.apache.org/jira/browse/RANGER-3759 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-RANGER-3759-Add-default-logback-configuration-for-tr.patch > > > We have migrated from log4j to logback for plugins but the default log level > of logback configuration is set at DEBUG to Console. This produces > unnecessarily detailed logs in the trino server log file. To solve this I > will add a trino-ranger-plugin-logback.xml file where users can tune the log > level for the trino plugin according to their needs. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (RANGER-3760) Make trino plugin configurable for trino environment running in docker
[ https://issues.apache.org/jira/browse/RANGER-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3760: Attachment: 0001-RANGER-3760-Make-trino-plugin-configurable-when-trin.patch > Make trino plugin configurable for trino environment running in docker > -- > > Key: RANGER-3760 > URL: https://issues.apache.org/jira/browse/RANGER-3760 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-RANGER-3760-Make-trino-plugin-configurable-when-trin.patch > > > Trino uses different plugin directories for server-type installation and > docker installation. > The plugin directory needs to be configured as /usr/lib/trino/plugin/ranger > when running in docker. > > Lets make this configurable in install.properties using new property > > INSTALL_ENV=docker > > If the user configures this property then trino-ranger-plugin will configure > the plugin directory to /usr/lib/trino/plugin/ranger > > otherwise, it will assume that trino is installed using a non-docker > environment and use the default plugin directory location -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (RANGER-3760) Make trino plugin configurable for trino environment running in docker
[ https://issues.apache.org/jira/browse/RANGER-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3760: Attachment: (was: 0001-RANGER-3760-Make-trino-plugin-configurable-when-trin.patch) > Make trino plugin configurable for trino environment running in docker > -- > > Key: RANGER-3760 > URL: https://issues.apache.org/jira/browse/RANGER-3760 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > Trino uses different plugin directories for server-type installation and > docker installation. > The plugin directory needs to be configured as /usr/lib/trino/plugin/ranger > when running in docker. > > Lets make this configurable in install.properties using new property > > INSTALL_ENV=docker > > If the user configures this property then trino-ranger-plugin will configure > the plugin directory to /usr/lib/trino/plugin/ranger > > otherwise, it will assume that trino is installed using a non-docker > environment and use the default plugin directory location -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (RANGER-3760) Make trino plugin configurable for trino environment running in docker
[ https://issues.apache.org/jira/browse/RANGER-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aakash Nand updated RANGER-3760: Attachment: 0001-RANGER-3760-Make-trino-plugin-configurable-when-trin.patch > Make trino plugin configurable for trino environment running in docker > -- > > Key: RANGER-3760 > URL: https://issues.apache.org/jira/browse/RANGER-3760 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-RANGER-3760-Make-trino-plugin-configurable-when-trin.patch > > > Trino uses different plugin directories for server-type installation and > docker installation. > The plugin directory needs to be configured as /usr/lib/trino/plugin/ranger > when running in docker. > > Lets make this configurable in install.properties using new property > > INSTALL_ENV=docker > > If the user configures this property then trino-ranger-plugin will configure > the plugin directory to /usr/lib/trino/plugin/ranger > > otherwise, it will assume that trino is installed using a non-docker > environment and use the default plugin directory location -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3760) Make trino plugin configurable for trino environment running in docker
[ https://issues.apache.org/jira/browse/RANGER-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537649#comment-17537649 ] Aakash Nand commented on RANGER-3760: - [~rmani] Here is the review request for this issue https://reviews.apache.org/r/73988/ > Make trino plugin configurable for trino environment running in docker > -- > > Key: RANGER-3760 > URL: https://issues.apache.org/jira/browse/RANGER-3760 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-RANGER-3760-Make-trino-plugin-configurable-when-trin.patch > > > Trino uses different plugin directories for server-type installation and > docker installation. > The plugin directory needs to be configured as /usr/lib/trino/plugin/ranger > when running in docker. > > Lets make this configurable in install.properties using new property > > INSTALL_ENV=docker > > If the user configures this property then trino-ranger-plugin will configure > the plugin directory to /usr/lib/trino/plugin/ranger > > otherwise, it will assume that trino is installed using a non-docker > environment and use the default plugin directory location -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537652#comment-17537652 ] Aakash Nand commented on RANGER-3755: - [~rmani] I have finished the patches for each issue, please apply them in the following order hopefully it will not create conflict. # RANGER-3182 # RANGER-3755 # RANGER-3759 # RANGER-3760 Let me know if there is any issue in applying these patches or if you have any feedback > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3751) ElasticSearch Audit shows wrong date on Ranger-admin UI
[
https://issues.apache.org/jira/browse/RANGER-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540004#comment-17540004
]
Aakash Nand commented on RANGER-3751:
-
[~pradeepagrawal8184] Please take a look at this whenever you get time.
Mentioning you since I saw your commit from above link
> ElasticSearch Audit shows wrong date on Ranger-admin UI
> ---
>
> Key: RANGER-3751
> URL: https://issues.apache.org/jira/browse/RANGER-3751
> Project: Ranger
> Issue Type: Bug
> Components: admin, audit
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Attachments: admin-ui-audit-screen.png
>
>
> Recently AmazonCloudWatch support was added to the audit module in this
> commit.
> However, this commit also changed the _toDate_ method of
> _ElasticSearchAccessAuditsService.java_ because of which the event time on
> the Audit screen is showing the wrong date from 1970. The error stack is as
> follows:
> {noformat}
> 2022-05-08 07:04:22,887 [http-nio-6080-exec-6] ERROR [MiscUtil.java:938]
> Error converting value to date. Value = 2022-05-08T06:42:01.621Z
> java.lang.IllegalArgumentException: null
> at java.base/java.util.Date.parse(Date.java:616)
> at java.base/java.util.Date.(Date.java:274)
> at org.apache.ranger.audit.provider.MiscUtil.toDate(MiscUtil.java:936)
> at
> org.apache.ranger.elasticsearch.ElasticSearchAccessAuditsService.populateViewBean(ElasticSearchAccessAuditsService.java:260)
> at
> org.apache.ranger.elasticsearch.ElasticSearchAccessAuditsService.searchXAccessAudits(ElasticSearchAccessAuditsService.java:95)
> at org.apache.ranger.biz.AssetMgr.getAccessLogs(AssetMgr.java:1139)
> at org.apache.ranger.rest.AssetREST.getAccessLogs(AssetREST.java:672)
> at
> org.apache.ranger.rest.AssetREST$$FastClassBySpringCGLIB$$8cffcb6d.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
> at
> org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:61)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123){noformat}
>
>
> The screenshot shows the erroneous date on ranger-admin
>
> Please refer:
> https://github.com/apache/ranger/commit/71744d3ff8e0db7f0a49881a891e77edf0ea518d#r73132360
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
Aakash Nand created RANGER-3772: --- Summary: Add dnsjava-2.1.7 dependency for trino plugin Key: RANGER-3772 URL: https://issues.apache.org/jira/browse/RANGER-3772 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: 2.3.0 Reporter: Aakash Nand The 2.3.0 version has upgraded the Hadoop dependency for various plugins and the current Hadoop version 3.3.0 gives problems because of Illegal access warnings. See https://issues.apache.org/jira/browse/HADOOP-17317 To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the log 2022-05-23T08:29:17.467ZERROR mainio.trino.server.Server Unable to create injector, see the following errors: 1) Error injecting constructor, java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44) at org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45) while locating org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl 1 error com.google.inject.CreationException: Unable to create injector, see the following errors: 1) Error injecting constructor, java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44) at org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45) while locating org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl 1 error at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543) at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109) at com.google.inject.Guice.createInjector(Guice.java:87) at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262) at org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53) at io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182) at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195) at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948) at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484) at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913) at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578) at io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151) at io.trino.server.Server.doStart(Server.java:135) at io.trino.server.Server.lambda$start$0(Server.java:80) at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source) at io.trino.server.Server.start(Server.java:80) at io.trino.server.TrinoServer.main(TrinoServer.java:38) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67) at org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance() at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114) at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32) at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112) at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120) at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:9
[jira] [Updated] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3772:
Description:
The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
the current Hadoop version 3.3.0 gives problems because of Illegal access
warnings. See
https://issues.apache.org/jira/browse/HADOOP-17317
To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the log
{code:java}
2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
injector, see the following errors:
1) Error injecting constructor, java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
at
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
while locating
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
1 error
com.google.inject.CreationException: Unable to create injector, see the
following errors:
1) Error injecting constructor, java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
at
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
while locating
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
1 error
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
at
com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
at com.google.inject.Guice.createInjector(Guice.java:87)
at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
at
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
at
io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
at
java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at
io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
at io.trino.server.Server.doStart(Server.java:135)
at io.trino.server.Server.lambda$start$0(Server.java:80)
at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
at io.trino.server.Server.start(Server.java:80)
at io.trino.server.TrinoServer.main(TrinoServer.java:38)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
at
org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
at
com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
at
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
at
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
at
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
at
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
at
com.google.inject.internal.InternalInjectorCreator.loa
[jira] [Commented] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540830#comment-17540830
]
Aakash Nand commented on RANGER-3772:
-
[~rmani], I have discovered this error after further thorough testing for the
trino-plugin. I can send a patch for this, can this be made available in
release-2.3?
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
> at
> com.go
[jira] [Updated] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3772:
Labels: Trino (was: )
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Labels: Trino
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
> at
> com.google.inject.internal.ProvisionListenerSta
[jira] [Comment Edited] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540830#comment-17540830
]
Aakash Nand edited comment on RANGER-3772 at 5/23/22 8:42 AM:
--
[~rmani], I have discovered this error after further thorough testing for the
trino-plugin. I can send a patch for this, can this be made available in stable
release-2.3?
was (Author: aakashnand):
[~rmani], I have discovered this error after further thorough testing for the
trino-plugin. I can send a patch for this, can this be made available in
release-2.3?
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.ca
[jira] [Updated] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3772:
Attachment: 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Labels: Trino
> Attachments:
> 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
>
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
> at
> com.google.inject.internal.Provis
[jira] [Commented] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540843#comment-17540843
]
Aakash Nand commented on RANGER-3772:
-
[~rmani] Submitted a patch and review request
https://reviews.apache.org/r/73997/
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Labels: Trino
> Attachments:
> 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
>
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleModule.provision(Lif
[jira] [Commented] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540965#comment-17540965
]
Aakash Nand commented on RANGER-3772:
-
You mean keeping this issue open until the next release and using this as a
document if we face an issue right?
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Labels: Trino
> Attachments:
> 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
>
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstra
[jira] [Updated] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3772:
Issue Type: Bug (was: Improvement)
Priority: Critical (was: Major)
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Critical
> Labels: Trino
> Attachments:
> 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
>
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
> at
> com.google.inject.internal.ProvisionL
[jira] [Commented] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540990#comment-17540990
]
Aakash Nand commented on RANGER-3772:
-
Got it. In that case could you please review it and if no problem commit it to
master for 3.0.0 version
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Critical
> Labels: Trino
> Attachments:
> 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
>
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleMod
[jira] [Commented] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541778#comment-17541778
]
Aakash Nand commented on RANGER-3772:
-
[~rmani] thank you for the comment, I have filled in the other details.
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Critical
> Labels: Trino
> Attachments:
> 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
>
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.ja
[jira] [Commented] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[
https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542027#comment-17542027
]
Aakash Nand commented on RANGER-3755:
-
[~williamlam] I see where you are coming from, I have faced this issue. This is
not a bug but a design. The distro module is usually built at the last after
all plugins are built so that is the reason why you are not able to see the tar
file. So to build the single trino-plugin and still get the tar file, you need
to add the following to root pom.xml under
{noformat}
ranger-trino-plugin
agents-audit
agents-common
agents-cred
agents-installer
credentialbuilder
ranger-plugin-classloader
ranger-util
plugin-trino
ranger-trino-plugin-shim
distro > ADD THIS LINE between Line Number 630 and
640
{noformat}
Once you add this distro line you can try one of the the following which will
build only trino plugin for you and still create a tar file
{code:java}
mvn clean install -P 'ranger-trino-plugin,!ranger-jdk11' -am{code}
or
{code:java}
mvn clean compile package assembly:assembly -P ranger-trino-plugin{code}
> Build Plugin-Trino artifacts only with JDK 11
> -
>
> Key: RANGER-3755
> URL: https://issues.apache.org/jira/browse/RANGER-3755
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Plugin Trino needs jdk 11 and about to compile and build. In order to avoid
> build issue in Apache Ranger when including Plugin Trino, we need to enable a
> profile so that default build of Apache Ranger will use JDK 1.8 and Plugin
> Trino and its artifacts can be build with JDK 11 profile.
> To build Plugin Trino artifacts following command can be executed.
> mvn clean compile package -P ranger-trino-plugin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (RANGER-3772) Add dnsjava-2.1.7 dependency for trino plugin
[
https://issues.apache.org/jira/browse/RANGER-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542418#comment-17542418
]
Aakash Nand commented on RANGER-3772:
-
Wow thank you so much
> Add dnsjava-2.1.7 dependency for trino plugin
> --
>
> Key: RANGER-3772
> URL: https://issues.apache.org/jira/browse/RANGER-3772
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Critical
> Labels: Trino
> Fix For: 3.0.0, 2.3.0
>
> Attachments:
> 0001-RANGER-3772-Add-dnsjava-dependency-to-trino-plugin.patch
>
>
> The 2.3.0 version has upgraded the Hadoop dependency for various plugins and
> the current Hadoop version 3.3.0 gives problems because of Illegal access
> warnings. See
> https://issues.apache.org/jira/browse/HADOOP-17317
> To solve this trino plugin needs dnsjava-2.1.7 dependency. Following is the
> log
>
> {code:java}
> 2022-05-23T08:29:17.467Z ERROR main io.trino.server.Server Unable to create
> injector, see the following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) Error injecting constructor, java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:44)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.lambda$create$0(RangerSystemAccessControlFactory.java:45)
> while locating
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:543)
> at
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)
> at com.google.inject.Guice.createInjector(Guice.java:87)
> at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:262)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlFactory.create(RangerSystemAccessControlFactory.java:53)
> at
> io.trino.security.AccessControlManager.createSystemAccessControl(AccessControlManager.java:182)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
> at
> java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
> at
> io.trino.security.AccessControlManager.loadSystemAccessControl(AccessControlManager.java:151)
> at io.trino.server.Server.doStart(Server.java:135)
> at io.trino.server.Server.lambda$start$0(Server.java:80)
> at io.trino.$gen.Trino_37320220523_082857_1.run(Unknown Source)
> at io.trino.server.Server.start(Server.java:80)
> at io.trino.server.TrinoServer.main(TrinoServer.java:38)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:67)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl$$FastClassByGuice$$f94a7f6a.newInstance()
> at
> com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
> at
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
> at
> com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
> at
> com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
> at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
> at
