[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=17557821#comment-17557821
]
Ishan Patwa edited comment on RANGER-3755 at 6/23/22 5:41 AM:
--
This is probably not related specially to this Issue but when I try to build
range-2.3 I am seeing the same errors.
Wondering if anyone was able to figure out what's going on
{code:java}
mvn -DskipTests=true clean compile package install assembly:assembly {code}
{code:java}
[INFO] Building tar: /home/ispatw/git/ranger/target/ranger-2.3.0-admin.tar.gz
[WARNING] When creating tar entry
org.codehaus.plexus.archiver.ArchiverException: Problem reading from source
file in xAR operation Unexpected end of ZLIB input stream
at org.codehaus.plexus.archiver.util.Streams.copyFullyDontCloseOutput
(Streams.java:131)
at org.codehaus.plexus.archiver.tar.TarArchiver.tarFile
(TarArchiver.java:318)
at org.codehaus.plexus.archiver.tar.TarArchiver.execute
(TarArchiver.java:171)
at org.codehaus.plexus.archiver.AbstractArchiver.createArchive
(AbstractArchiver.java:916)
at
org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive
(AssemblyProxyArchiver.java:445)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive
(DefaultAssemblyArchiver.java:181)
at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute
(AbstractAssemblyMojo.java:484)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions
(MojoExecutor.java:355)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:200)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
[INFO]
[INFO] Reactor Summary for ranger 2.3.0:
[INFO]
[INFO] ranger . FAILURE [01:40 min]
[INFO] Jdbc SQL Connector . SUCCESS [ 7.513 s]
[INFO] Credential Support . SUCCESS [ 8.309 s]
[INFO] Audit Component SUCCESS [ 18.598 s]
[INFO] ranger-plugin-classloader .. SUCCESS [ 6.812 s]
[INFO] Common library for Plugins . SUCCESS [ 32.311 s]
[INFO] ranger-intg SUCCESS [ 9.202 s]
[INFO] Installer Support Component SUCCESS [ 4.478 s]
[INFO] Credential Builder . SUCCESS [ 8.817 s]
[INFO] Embedded Web Server Invoker SUCCESS [ 27.438 s]
[INFO] Key Management Service . SUCCESS [ 35.111 s]
[INFO] HBase Security Plugin Shim . SUCCESS [ 11.359 s]
[INFO] HBase Security Plugin .. SUCCESS [ 18.389 s]
[INFO] Hdfs
[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=17557821#comment-17557821
]
Ishan Patwa commented on RANGER-3755:
-
This is probably not related specially to this Issue but when I try to build
range-2.3 I am seeing the same errors.
Wondering if anyone was able to figure out what's going on
{code:java}
[INFO] Building tar: /home/ispatw/git/ranger/target/ranger-2.3.0-admin.tar.gz
[WARNING] When creating tar entry
org.codehaus.plexus.archiver.ArchiverException: Problem reading from source
file in xAR operation Unexpected end of ZLIB input stream
at org.codehaus.plexus.archiver.util.Streams.copyFullyDontCloseOutput
(Streams.java:131)
at org.codehaus.plexus.archiver.tar.TarArchiver.tarFile
(TarArchiver.java:318)
at org.codehaus.plexus.archiver.tar.TarArchiver.execute
(TarArchiver.java:171)
at org.codehaus.plexus.archiver.AbstractArchiver.createArchive
(AbstractArchiver.java:916)
at
org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive
(AssemblyProxyArchiver.java:445)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive
(DefaultAssemblyArchiver.java:181)
at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute
(AbstractAssemblyMojo.java:484)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions
(MojoExecutor.java:355)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:200)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
[INFO]
[INFO] Reactor Summary for ranger 2.3.0:
[INFO]
[INFO] ranger . FAILURE [01:40 min]
[INFO] Jdbc SQL Connector . SUCCESS [ 7.513 s]
[INFO] Credential Support . SUCCESS [ 8.309 s]
[INFO] Audit Component SUCCESS [ 18.598 s]
[INFO] ranger-plugin-classloader .. SUCCESS [ 6.812 s]
[INFO] Common library for Plugins . SUCCESS [ 32.311 s]
[INFO] ranger-intg SUCCESS [ 9.202 s]
[INFO] Installer Support Component SUCCESS [ 4.478 s]
[INFO] Credential Builder . SUCCESS [ 8.817 s]
[INFO] Embedded Web Server Invoker SUCCESS [ 27.438 s]
[INFO] Key Management Service . SUCCESS [ 35.111 s]
[INFO] HBase Security Plugin Shim . SUCCESS [ 11.359 s]
[INFO] HBase Security Plugin .. SUCCESS [ 18.389 s]
[INFO] Hdfs Security Plugin ... SUCCESS [ 16.514 s]
[INFO] Hive Security Plugin ... SUCCESS [
[jira] [Created] (RANGER-3801) Add Dockerfile.ranger-ozone and docker-compose.ranger-ozone.yml
Siyao Meng created RANGER-3801: -- Summary: Add Dockerfile.ranger-ozone and docker-compose.ranger-ozone.yml Key: RANGER-3801 URL: https://issues.apache.org/jira/browse/RANGER-3801 Project: Ranger Issue Type: Task Components: build-infra Reporter: Siyao Meng Hi folks, I see Ranger has dev support for hadoop, hbase, hive, solr and others. Shall we add ozone as well? As Ozone does support using [RangerOzoneAuthorizer|https://github.com/apache/ranger/blob/master/plugin-ozone/src/main/java/org/apache/ranger/authorization/ozone/authorizer/RangerOzoneAuthorizer.java] as the ACL checker? https://github.com/apache/ranger/tree/master/dev-support/ranger-docker Thanks. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (RANGER-3790) Ranger tagsync module should not depend on kafka server
[ https://issues.apache.org/jira/browse/RANGER-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557515#comment-17557515 ] Patrik Márton edited comment on RANGER-3790 at 6/22/22 3:20 PM: Review board: [https://reviews.apache.org/r/74035/] PR: [https://github.com/apache/ranger/pull/154] was (Author: JIRAUSER290945): Review board: https://reviews.apache.org/r/74035/ > Ranger tagsync module should not depend on kafka server > --- > > Key: RANGER-3790 > URL: https://issues.apache.org/jira/browse/RANGER-3790 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: 3.0.0 >Reporter: Patrik Márton >Assignee: Patrik Márton >Priority: Major > Attachments: RANGER-3790.patch > > Time Spent: 10m > Remaining Estimate: 0h > > This is a follow-up of RANGER-2426. > Kafka Core dependency has already been removed from tagsync as part of the > mentioned ticket, but since the _distro/src/main/assembly/tagsync.xml_ > contains this dependency, it is included in the distribution. > [https://github.com/apache/ranger/blob/master/distro/src/main/assembly/tagsync.xml#L56] > > The goal is to remove this from the assembly. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [ranger] patrik-marton opened a new pull request, #154: RANGER-3790: Ranger tagsync module should not depend on kafka server
patrik-marton opened a new pull request, #154: URL: https://github.com/apache/ranger/pull/154 This commit removes the unused kafka core dependency from the assembly xml of the tagsync module, so it will not be added to the distribution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (RANGER-3790) Ranger tagsync module should not depend on kafka server
[ https://issues.apache.org/jira/browse/RANGER-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557515#comment-17557515 ] Patrik Márton commented on RANGER-3790: --- Review board: https://reviews.apache.org/r/74035/ > Ranger tagsync module should not depend on kafka server > --- > > Key: RANGER-3790 > URL: https://issues.apache.org/jira/browse/RANGER-3790 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: 3.0.0 >Reporter: Patrik Márton >Assignee: Patrik Márton >Priority: Major > Attachments: RANGER-3790.patch > > > This is a follow-up of RANGER-2426. > Kafka Core dependency has already been removed from tagsync as part of the > mentioned ticket, but since the _distro/src/main/assembly/tagsync.xml_ > contains this dependency, it is included in the distribution. > [https://github.com/apache/ranger/blob/master/distro/src/main/assembly/tagsync.xml#L56] > > The goal is to remove this from the assembly. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
Review Request 74035: RANGER-3790: Ranger tagsync module should not depend on kafka server
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74035/ --- Review request for ranger. Repository: ranger Description --- This commit removes the unused kafka core dependency from the assembly xml of the tagsync module, so it will not be added to the distribution. Diffs - distro/src/main/assembly/tagsync.xml c467e5a97 Diff: https://reviews.apache.org/r/74035/diff/1/ Testing --- Tested manually by checking the dependencies for tagsync module in the distribution. Thanks, Patrik Márton
[jira] [Updated] (RANGER-3790) Ranger tagsync module should not depend on kafka server
[ https://issues.apache.org/jira/browse/RANGER-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrik Márton updated RANGER-3790: -- Attachment: RANGER-3790.patch > Ranger tagsync module should not depend on kafka server > --- > > Key: RANGER-3790 > URL: https://issues.apache.org/jira/browse/RANGER-3790 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: 3.0.0 >Reporter: Patrik Márton >Assignee: Patrik Márton >Priority: Major > Attachments: RANGER-3790.patch > > > This is a follow-up of RANGER-2426. > Kafka Core dependency has already been removed from tagsync as part of the > mentioned ticket, but since the _distro/src/main/assembly/tagsync.xml_ > contains this dependency, it is included in the distribution. > [https://github.com/apache/ranger/blob/master/distro/src/main/assembly/tagsync.xml#L56] > > The goal is to remove this from the assembly. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3800) Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties methods in trino-plugin
[
https://issues.apache.org/jira/browse/RANGER-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557322#comment-17557322
]
Aakash Nand commented on RANGER-3800:
-
[~rmani] , [~pradeepagrawal8184], [~mehul] I have created Review here please
check https://reviews.apache.org/r/74034/
> Add unimplemented checkCanSetTableAuthorization and
> checkCanSetTableProperties methods in trino-plugin
> --
>
> Key: RANGER-3800
> URL: https://issues.apache.org/jira/browse/RANGER-3800
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-3800-Add-unimplemented-methods-for-trino-plug.patch
>
>
> {color:#de350b}checkCanSetTableAuthorization{color} and
> {color:#de350b}checkCanSetTableProperties{color} methods are not implemented
> in trino-ranger-plugin this gives `AccessDeniedException` when executing
> queries like
>
> {{ALTER TABLE XXX SET AUTHORIZATION}}
>
>
> and
>
> {{ALTER TABLE XXX SET PROPERTIES}}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
Review Request 74034: RANGER-3800 : Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties methods in trino-plugin
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74034/ --- Review request for ranger, Mehul Parikh, Pradeep Agrawal, and Ramesh Mani. Bugs: RANGER-3800 https://issues.apache.org/jira/browse/RANGER-3800 Repository: ranger Description --- checkCanSetTableAuthorization and checkCanSetTableProperties methods are not implemented in trino-ranger-plugin this gives `AccessDeniedException` when executing queries like ALTER TABLE XXX SET AUTHORIZATION and ALTER TABLE XXX SET PROPERTIES Diffs - plugin-trino/src/main/java/org/apache/ranger/authorization/trino/authorizer/RangerSystemAccessControl.java cc06187f4 ranger-trino-plugin-shim/src/main/java/org/apache/ranger/authorization/trino/authorizer/RangerSystemAccessControl.java c6b234dc2 Diff: https://reviews.apache.org/r/74034/diff/1/ Testing --- Deployed plugin locally and confirmed the query execution Thanks, Aakash Nand
[jira] [Updated] (RANGER-3800) Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties methods in trino-plugin
[
https://issues.apache.org/jira/browse/RANGER-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3800:
Attachment: 0001-RANGER-3800-Add-unimplemented-methods-for-trino-plug.patch
> Add unimplemented checkCanSetTableAuthorization and
> checkCanSetTableProperties methods in trino-plugin
> --
>
> Key: RANGER-3800
> URL: https://issues.apache.org/jira/browse/RANGER-3800
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-3800-Add-unimplemented-methods-for-trino-plug.patch
>
>
> {color:#de350b}checkCanSetTableAuthorization{color} and
> {color:#de350b}checkCanSetTableProperties{color} methods are not implemented
> in trino-ranger-plugin this gives `AccessDeniedException` when executing
> queries like
>
> {{ALTER TABLE XXX SET AUTHORIZATION}}
>
>
> and
>
> {{ALTER TABLE XXX SET PROPERTIES}}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (RANGER-3800) Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties methods in trino-plugin
[
https://issues.apache.org/jira/browse/RANGER-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3800:
Summary: Add unimplemented checkCanSetTableAuthorization and
checkCanSetTableProperties methods in trino-plugin (was: Add unimplemented
checkCanSetTableAuthorization and checkCanSetTableProperties method)
> Add unimplemented checkCanSetTableAuthorization and
> checkCanSetTableProperties methods in trino-plugin
> --
>
> Key: RANGER-3800
> URL: https://issues.apache.org/jira/browse/RANGER-3800
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Fix For: 3.0.0
>
>
> {color:#de350b}checkCanSetTableAuthorization{color} and
> {color:#de350b}checkCanSetTableProperties{color} methods are not implemented
> in trino-ranger-plugin this gives `AccessDeniedException` when executing
> queries like
>
> {{ALTER TABLE XXX SET AUTHORIZATION}}
>
>
> and
>
> {{ALTER TABLE XXX SET PROPERTIES}}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (RANGER-3800) Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties method
[
https://issues.apache.org/jira/browse/RANGER-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aakash Nand updated RANGER-3800:
Description:
{color:#de350b}checkCanSetTableAuthorization{color} and
{color:#de350b}checkCanSetTableProperties{color} methods are not implemented in
trino-ranger-plugin this gives `AccessDeniedException` when executing queries
like
{{ALTER TABLE XXX SET AUTHORIZATION}}
and
{{ALTER TABLE XXX SET PROPERTIES}}
was:
`checkCanSetTableAuthorization` and `checkCanSetTableProperties` methods are
not implemented in trino-ranger-plugin this gives `AccessDeniedException` when
executing queries like
```
ALTER TABLE XXX SET AUTHORIZATION
```
and
```
ALTER TABLE XXX SET PROPERTIES
```
> Add unimplemented checkCanSetTableAuthorization and
> checkCanSetTableProperties method
> -
>
> Key: RANGER-3800
> URL: https://issues.apache.org/jira/browse/RANGER-3800
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Fix For: 3.0.0
>
>
> {color:#de350b}checkCanSetTableAuthorization{color} and
> {color:#de350b}checkCanSetTableProperties{color} methods are not implemented
> in trino-ranger-plugin this gives `AccessDeniedException` when executing
> queries like
>
> {{ALTER TABLE XXX SET AUTHORIZATION}}
>
>
> and
>
> {{ALTER TABLE XXX SET PROPERTIES}}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (RANGER-3800) Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties method
Aakash Nand created RANGER-3800: --- Summary: Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties method Key: RANGER-3800 URL: https://issues.apache.org/jira/browse/RANGER-3800 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: 2.3.0 Reporter: Aakash Nand Fix For: 3.0.0 `checkCanSetTableAuthorization` and `checkCanSetTableProperties` methods are not implemented in trino-ranger-plugin this gives `AccessDeniedException` when executing queries like ``` ALTER TABLE XXX SET AUTHORIZATION ``` and ``` ALTER TABLE XXX SET PROPERTIES ``` -- This message was sent by Atlassian Jira (v8.20.7#820007)
Re: [VOTE] Release Apache Ranger version 2.3.0 - rc2
Dear Rangers, Ranger Community has reported a build issue with Apache Ranger 2.3.0 rc#2 Apache Ranger 2.3.0 rc#2 can be built only with maven 3.6.3 and this is related to the Apache Solr version which is used. Backported https://issues.apache.org/jira/browse/RANGER-3091 from Apache Ranger 3.0.0 branch and verified the build. Now the build went successful with different versions of maven. Audit to Solr also looks good in docker. To address this Apache Ranger 2.3.0 rc#3 artifacts have to be created. Also there was an ask for including RANGER-3730 which can be considered for rc#3 release after review. Stay tuned and thank you for all your support. Regards, Ramesh On Tue, Jun 21, 2022 at 8:38 PM KirbY ZhoU wrote: > +1 > > But I suggest include RANGER-3730 to avoid log4j-1.2 > > > 在 2022/6/16 14:23，“Ramesh Mani” 写入: > > Dear Rangers, > > Apache Ranger 2.3.0 release candidate #2 is now available for a vote > within > the dev community. Links to the release artifacts are given below. > Please > review and vote. > > The vote will be open for at least 72 hours or until necessary votes > are > reached. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks, > Ramesh > > List of all issues / improvements addressed in this release: > https://issues.apache.org/jira/issues/?jql=project=RANGER AND > status=Resolved AND fixVersion=2.3.0 ORDER BY key DESC > > Git tag for the release: > https://github.com/apache/ranger/tree/release-2.3.0-rc2 > > Sources for the release: > > https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc2/apache-ranger-2.3.0.tar.gz > > Source release verification: > PGP Signature: > > https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc2/apache-ranger-2.3.0.tar.gz.asc > SHA256 Hash: > > https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc2/apache-ranger-2.3.0.tar.gz.sha256 > SHA512 Hash: > > https://dist.apache.org/repos/dist/dev/ranger/2.3.0-rc2/apache-ranger-2.3.0.tar.gz.sha512 > > Keys to verify the signature of the release artifacts are available at: > https://dist.apache.org/repos/dist/release/ranger/KEYS > > New features/enhancements: > > RANGER-2846 Add support for resource[volume, bucket, key] look up in > ozone > plugin > RANGER-2967 Add support for Amazon CloudWatch Logs as an Audit Store > RANGER-3023 Permission tab takes longer time to load with large number > of > users and group_users data > RANGER-3030 Replace Findbugs with Spotbugs maven plugin > RANGER-3182 Prestosql is renamed to Trino > RANGER-3221 Improve logging in Presto plugin > RANGER-3276 Remove duplicate code from buildks.java > RANGER-3290 ArrayIndexOutOfBoundsException if solr is down > RANGER-3299 Upgrading the bouncycastle version for bcprov-jdk15on > RANGER-3298 Add coarse URI check for Hive Agent > RANGER-3389 Swagger UI Support for Ranger REST API > RANGER-3435 Add unique index on guid, service and zone_id column of > x_policy table > RANGER-3439 Add rest api to get or delete ranger policy based on guid > RANGER-3455 [Logout-Ranger] Should either be disabled/ should redirect > to > knox logout page > RANGER-3459 Upgrade Ranger's Kafka dependency to 2.8 > RANGER-3475 Promote TagRest endpoints to /public/v2 > RANGER-3487 Update underscore js with latest version. > RANGER-3493 Add unique index on service and resource_signature column > of > x_policy table > RANGER-3498 RANGER : Remove log4j1 dependencies. > RANGER-3504 Create framework to execute DB patch dependent on Java > patch. > RANGER-3510 Ranger upgrade spring framework version to 5.3.12 > RANGER-3511 Create Java patch to update policy resource-signature to > unique > value. > RANGER-3512 Create Java patch to update policy guid to unique value. > RANGER-3515 Enhance Ranger Java client SSL config to be configured > using > serviceType and AppId > RANGER-3518 Limit the query size stored in Audit logs > RANGER-3521 Ranger KMS IS NOT ENFORCING HSTS ON SSL PORT DEFINED BY > RFC 6797 > RANGER-3526 policy evaluation ordering to use name as secondary > sorting key > RANGER-3533 Provide sorting on columns throughout the audits result > set and > policy listing page. > RANGER-3538 Reduce the granularity of locking when building/retrieving > a > policy-engine within Ranger admin service > RANGER-3539 Add jacoco-maven-plugin for code coverage > RANGER-3540 Add support to read audit logs from Amazon CloudWatch > RANGER-3545 Remove Logger Checks for Info Enabled > RANGER-3548 Update performance engine test scripts > RANGER-3550 support for using user/tag attributes in row-filter > expressions > and conditions > RANGER-3551 Analyze & optimize module permissions related API > RANGER-3553 Unit test coverage for XUserMgr and UserMgr class >
