[jira] [Assigned] (RANGER-4404) Audit to hdfs for orc format feature stabilisation
[
https://issues.apache.org/jira/browse/RANGER-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhavik Patel reassigned RANGER-4404:
Assignee: (was: Bhavik Patel)
> Audit to hdfs for orc format feature stabilisation
> --
>
> Key: RANGER-4404
> URL: https://issues.apache.org/jira/browse/RANGER-4404
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Bhavik Patel
>Priority: Major
>
> Currently if we have 50GB audit log file in spool directory then it is taking
> 4-5hr for the conversion and writing to HDFS.
> Also, we are observing below error logs
> {code:java}
> ERROR [AuditFileQueueSpool_hdfs_destWriter] provider.BaseAuditHandler: Error
> writing to log file.
> java.lang.RuntimeException: Overflow of newLength.
> smallBuffer.length=1073741824, nextElemLength=38
> at
> org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.increaseBufferSpace(BytesColumnVector.java:311)
> at
> org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:182)
> at
> org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector.setVal(BytesColumnVector.java:207)
> at org.apache.ranger.audit.utils.ORCFileUtil.log(ORCFileUtil.java:143)
> at
> org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:77)
> at
> org.apache.ranger.audit.utils.RangerORCAuditWriter$1.run(RangerORCAuditWriter.java:73)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1762)
> at
> org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:541)
> at
> org.apache.ranger.audit.utils.RangerORCAuditWriter.logAuditAsORC(RangerORCAuditWriter.java:73)
> at
> org.apache.ranger.audit.utils.RangerORCAuditWriter.logAsORC(RangerORCAuditWriter.java:159)
> at
> org.apache.ranger.audit.utils.RangerORCAuditWriter.log(RangerORCAuditWriter.java:112)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:78)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.log(HDFSAuditDestination.java:163)
> at
> org.apache.ranger.audit.queue.AuditFileQueueSpool.sendEvent(AuditFileQueueSpool.java:926)
> at
> org.apache.ranger.audit.queue.AuditFileQueueSpool.logEvent(AuditFileQueueSpool.java:913)
> at
> org.apache.ranger.audit.queue.AuditFileQueueSpool.runLogAudit(AuditFileQueueSpool.java:847)
> at
> org.apache.ranger.audit.queue.AuditFileQueueSpool.run(AuditFileQueueSpool.java:790)
> {code}
> hive-storage-api version upgrade(>=2.7.3) required to resolve the above error.
> Current version is 2.7.2
> cc: [~rmani] [~fateh288]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Close all merged review requests
Hello Dev, Kindly close all merged review requests from review board. Thanks, Bhavik Patel +91-7208744109
Re: Review Request 75203: RANGER-4833 : Upgrade from Bootbox.js to Bootprompt.js
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75203/#review226908 --- Ship it! Ship It! - bhavik patel On Sept. 9, 2024, 10:56 a.m., Dhaval Rajpara wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/75203/ > --- > > (Updated Sept. 9, 2024, 10:56 a.m.) > > > Review request for ranger, bhavik patel, Brijesh Bhalala, Dineshkumar Yadav, > Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Pradeep Agrawal, and Vishal > Bhavsar. > > > Bugs: RANGER-4833 > https://issues.apache.org/jira/browse/RANGER-4833 > > > Repository: ranger > > > Description > --- > > Upgrade from Bootbox.js to Bootprompt.js > > > Diffs > - > > security-admin/src/main/webapp/libs/bower/bootbox/js/bootbox.js e27cf404c > security-admin/src/main/webapp/libs/bower/bootprompt/bootprompt.js > PRE-CREATION > security-admin/src/main/webapp/scripts/Init.js 5909f93a9 > security-admin/src/main/webapp/scripts/routers/Router.js 448659eb2 > security-admin/src/main/webapp/scripts/utils/XALangSupport.js 1f8a08944 > security-admin/src/main/webapp/scripts/utils/XAUtils.js fc3ff5b5d > > security-admin/src/main/webapp/scripts/views/permissions/ModulePermsTableLayout.js > f53bb724e > security-admin/src/main/webapp/scripts/views/service/ServiceCreate.js > b980b0a70 > > > Diff: https://reviews.apache.org/r/75203/diff/1/ > > > Testing > --- > > Tested ranger admin with > 1) service crud opration > 2) policy crud opration > 3) user/group/role crud opration > 4) security zone crud opration > 5) import / export > And checked that all modal popup come properly. > > > Thanks, > > Dhaval Rajpara > >
[jira] [Updated] (RANGER-4814) Ranger - Upgrade Aircompressor to 0.27
[ https://issues.apache.org/jira/browse/RANGER-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4814: - Issue Type: Improvement (was: Task) > Ranger - Upgrade Aircompressor to 0.27 > -- > > Key: RANGER-4814 > URL: https://issues.apache.org/jira/browse/RANGER-4814 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dineshkumar Yadav >Assignee: Dineshkumar Yadav >Priority: Major > > Ranger - Upgrade Aircompressor to 0.27 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 75202: RANGER-4901 : [Ranger React UI] Admin audits for "Import Delete" operation type do not display service name field ;
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75202/#review226905 --- Ship it! Ship It! - bhavik patel On Sept. 9, 2024, 10:12 a.m., Dhaval Rajpara wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/75202/ > --- > > (Updated Sept. 9, 2024, 10:12 a.m.) > > > Review request for ranger, Abhishek Patil, bhavik patel, Brijesh Bhalala, > Dineshkumar Yadav, Madhan Neethiraj, Mehul Parikh, and Mugdha Varadkar. > > > Bugs: RANGER-4901 > https://issues.apache.org/jira/browse/RANGER-4901 > > > Repository: ranger > > > Description > --- > > In Ranger React UI, in admin audits, the "Service name" field is missing for > the audits of operation type "Import Delete". > In Backbone UI, for the same admin audits, the "Service name" field is > present. > > *Steps to reproduce :-* > 1. Login to Ranger admin UI > 2. Export the policies for any service, for e.g, cm_hdfs > 3. Import the policies from the json file which was obtained in step 2. While > importing the policies, check the override option. > 4. Navigate to the admin audits page, and in the admin audits page, audits > will be generated for "Import Delete" action. > 5. Click on any audit with the "Import Delete" action, in the popup, the > details are present for the policy which is deleted during the policy import > operation. > In the popup, the service name field is missing > 6. Now switch to Backbone UI, navigate to admin audits page, and click on the > same audit. In the popup, the service name field is present for the audit > > *Attachments :-* > 1. Screenshot 1 : Admin audit for "Import Delete" operation in Backbone UI, > displaying the service name field > 2. Screenshot 2 : Admin audit for "Import Delete" operation in React UI, > which does not contain the service name field > > > Diffs > - > > > security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyLogs.jsx > 85e64aa8a > > > Diff: https://reviews.apache.org/r/75202/diff/1/ > > > Testing > --- > > Tested that after this patch import delete policy log populate Service Name > field properly. > > > Thanks, > > Dhaval Rajpara > >
[jira] [Commented] (RANGER-4200) Upgrade jquery version to 3.6.1 in order to fix its own vulnerabilities
[ https://issues.apache.org/jira/browse/RANGER-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880210#comment-17880210 ] Bhavik Patel commented on RANGER-4200: -- [~dhavalrajpara] [~mugdha.varadkar] [~ni3galave] Can you kindly help to review the patch? > Upgrade jquery version to 3.6.1 in order to fix its own vulnerabilities > > > Key: RANGER-4200 > URL: https://issues.apache.org/jira/browse/RANGER-4200 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: chenyu >Assignee: chenyu >Priority: Major > Fix For: 3.0.0, 2.4.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4928) Upgrade Hbase shaded version to fix the Service Test Connection
Bhavik Patel created RANGER-4928: Summary: Upgrade Hbase shaded version to fix the Service Test Connection Key: RANGER-4928 URL: https://issues.apache.org/jira/browse/RANGER-4928 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade Hbase shaded version to fix the Service Test Connection https://issues.apache.org/jira/browse/HBASE-28793 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4076) Support Java 17 for build and runtime
[ https://issues.apache.org/jira/browse/RANGER-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878809#comment-17878809 ] Bhavik Patel commented on RANGER-4076: -- [~rakeshgupta264] Could you please verify if usersync, tagsync, and KMS functionality working correctly? During my validation with JDK-17, I noticed an issue with the jaxb-runtime dependency. Could you double check into this? Thank you for your efforts on this crucial feature support. > Support Java 17 for build and runtime > - > > Key: RANGER-4076 > URL: https://issues.apache.org/jira/browse/RANGER-4076 > Project: Ranger > Issue Type: New Feature > Components: admin, build-infra >Reporter: Andrew Luo >Assignee: Rakesh Gupta >Priority: Major > Attachments: > 0001-RANGER-4076-Support-Java-17-for-build-and-runtime.patch > > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4913) Upgrade commons-collections-3.2.2 to commons-collections4
Bhavik Patel created RANGER-4913: Summary: Upgrade commons-collections-3.2.2 to commons-collections4 Key: RANGER-4913 URL: https://issues.apache.org/jira/browse/RANGER-4913 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Bhavik Patel Upgrade commons-collections-3.2.2 to commons-collections4 as current version is at EOL -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4626) Ranger don’t support trino to enable kerberos
[ https://issues.apache.org/jira/browse/RANGER-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4626: - Issue Type: Improvement (was: New Feature) > Ranger don’t support trino to enable kerberos > - > > Key: RANGER-4626 > URL: https://issues.apache.org/jira/browse/RANGER-4626 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Yanxiang Qin >Priority: Major > Labels: Trino > Attachments: ranger.png, trino.png > > Time Spent: 20m > Remaining Estimate: 0h > > When trino to enable kerberos, the range Test Connection failed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4626) Ranger don’t support trino to enable kerberos
[
https://issues.apache.org/jira/browse/RANGER-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874113#comment-17874113
]
Bhavik Patel commented on RANGER-4626:
--
Thanks [~everypp] for working on this.
Can you update below line
{code:java}
"boolean kerberosEnabled =
Boolean.getBoolean(prop.getProperty("kerberos.enabled", "false"));"
to
"boolean kerberosEnabled = Boolean.valueOf(prop.getProperty("kerberos.enabled",
"false"));"{code}
> Ranger don’t support trino to enable kerberos
> -
>
> Key: RANGER-4626
> URL: https://issues.apache.org/jira/browse/RANGER-4626
> Project: Ranger
> Issue Type: New Feature
> Components: plugins
>Reporter: Yanxiang Qin
>Priority: Major
> Labels: Trino
> Attachments: ranger.png, trino.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When trino to enable kerberos, the range Test Connection failed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4865) Add allowPublicKeyRetrieval setting option
[ https://issues.apache.org/jira/browse/RANGER-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873472#comment-17873472 ] Bhavik Patel commented on RANGER-4865: -- Can you also update for the Ranger KMS as well? > Add allowPublicKeyRetrieval setting option > -- > > Key: RANGER-4865 > URL: https://issues.apache.org/jira/browse/RANGER-4865 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: KIM JI HYE >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > To use mysql 8, allowPublicKeyRetrieval setting is required. > Therefore, the allowPublicKeyRetrieval option was added to the ranger's > db_setup.py settings, and the integration between mysql8 and apache ranger > was successful. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4900) Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/RANGER-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872830#comment-17872830 ] Bhavik Patel commented on RANGER-4900: -- Commit link: https://github.com/apache/ranger/commit/dfb8c43a902894def0a27230e9b56f09cb55167e > Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT > -- > > Key: RANGER-4900 > URL: https://issues.apache.org/jira/browse/RANGER-4900 > Project: Ranger > Issue Type: Sub-task > Components: Ranger > Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > > Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4900) Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT
[ https://issues.apache.org/jira/browse/RANGER-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel resolved RANGER-4900. -- Resolution: Fixed > Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT > -- > > Key: RANGER-4900 > URL: https://issues.apache.org/jira/browse/RANGER-4900 > Project: Ranger > Issue Type: Sub-task > Components: Ranger > Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > > Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4900) Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT
Bhavik Patel created RANGER-4900: Summary: Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT Key: RANGER-4900 URL: https://issues.apache.org/jira/browse/RANGER-4900 Project: Ranger Issue Type: Sub-task Components: Ranger Reporter: Bhavik Patel Assignee: Bhavik Patel Update branch ranger-2.5 to produce 2.5.1-SNAPSHOT -- This message was sent by Atlassian Jira (v8.20.10#820010)
[ANNOUNCE] Apache Ranger 2.5.0 released
Hi, Apache Ranger team is happy to announce the release of Apache Ranger 2.5.0. Apache Ranger is a framework to enable, monitor and manage comprehensive data security across big-data and cloud platforms and beyond. Apache Ranger 2.5.0 contains a number of new features, improvements and bug fixes. Release details can be found in the release notes at https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+2.5.0+-+Release+Notes The release artifacts are available at: https://ranger.apache.org/download.html. The binary artifacts are available from Maven central and its mirrors. When downloading binaries from the site, please remember to verify the downloads using signatures found at: https://www.apache.org/dist/ranger/KEYS Additional details about Apache Ranger can be found at: https://ranger.apache.org We thank everyone who made this release possible. Thanks, Apache Ranger team
[ANNOUNCE] Apache Ranger 2.5.0 released
Hi, Apache Ranger team is happy to announce the release of Apache Ranger 2.5.0. Apache Ranger is a framework to enable, monitor and manage comprehensive data security across big-data and cloud platforms and beyond. Apache Ranger 2.5.0 contains a number of new features, improvements and bug fixes. Release details can be found in the release notes at https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+2.5.0+-+Release+Notes The release artifacts are available at: https://ranger.apache.org/download.html. The binary artifacts are available from Maven central and its mirrors. When downloading binaries from the site, please remember to verify the downloads using signatures found at: https://www.apache.org/dist/ranger/KEYS Additional details about Apache Ranger can be found at: https://ranger.apache.org We thank everyone who made this release possible. Thanks, Apache Ranger team
[jira] [Commented] (RANGER-4846) Update Apache Ranger website with 2.5.0
[ https://issues.apache.org/jira/browse/RANGER-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872191#comment-17872191 ] Bhavik Patel commented on RANGER-4846: -- Added new wiki pages for release-2.5.0 details : https://cwiki.apache.org/confluence/display/RANGER/2.5.0+release+-+Apache+Ranger > Update Apache Ranger website with 2.5.0 > --- > > Key: RANGER-4846 > URL: https://issues.apache.org/jira/browse/RANGER-4846 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Fix For: 2.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4847) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872189#comment-17872189 ] Bhavik Patel commented on RANGER-4847: -- Published Apache Ranger 2.5.0 binaries based on the -https://cwiki.apache.org/confluence/display/RANGER/Publishing+Apache+Ranger+artifacts+to+Maven+Central Release artifacts published : https://mvnrepository.com/artifact/org.apache.ranger/ranger-plugins-common/2.5.0 > Publish release artifacts > - > > Key: RANGER-4847 > URL: https://issues.apache.org/jira/browse/RANGER-4847 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Fix For: 2.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4847) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel resolved RANGER-4847. -- Resolution: Fixed > Publish release artifacts > - > > Key: RANGER-4847 > URL: https://issues.apache.org/jira/browse/RANGER-4847 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Bhavik Patel > Assignee: Bhavik Patel >Priority: Major > Fix For: 2.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 75147: RANGER-4846: Update Apache Ranger website with 2.5.0
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75147/ --- Review request for ranger, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, and Velmurugan Periasamy. Bugs: RANGER-4846 https://issues.apache.org/jira/browse/RANGER-4846 Repository: ranger Description --- RANGER-4846: Update Apache Ranger website with 2.5.0 Diffs - docs/src/site/site.xml 9eb4b3343 docs/src/site/xdoc/download.xml fecbe5bd9 Diff: https://reviews.apache.org/r/75147/diff/1/ Testing --- Thanks, bhavik patel
[jira] [Commented] (RANGER-4847) Publish release artifacts
[ https://issues.apache.org/jira/browse/RANGER-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871549#comment-17871549 ] Bhavik Patel commented on RANGER-4847: -- Committed the source artifacts & checksum artifacts from svn : https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/ to svn : https://dist.apache.org/repos/dist/release/ranger/2.5.0/ > Publish release artifacts > - > > Key: RANGER-4847 > URL: https://issues.apache.org/jira/browse/RANGER-4847 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Fix For: 2.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4892) Upgrade Ranger Tomcat from 8.5.x to 9.x
Bhavik Patel created RANGER-4892: Summary: Upgrade Ranger Tomcat from 8.5.x to 9.x Key: RANGER-4892 URL: https://issues.apache.org/jira/browse/RANGER-4892 Project: Ranger Issue Type: Improvement Components: kms, Ranger Affects Versions: 3.0.0 Reporter: Bhavik Patel Upgrade Ranger Tomcat from 8.5.x to 9.x as latest version of tomcat 8.5.100 is impacted with critical vulnerability -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Apache Ranger version 2.5.0 - RC4
Hello Rangers, Thanks for taking your active participation in verify, giving the feedback and voting on Apache Ranger 2.5.0 release candidate #4. More than 72 hours have passed since the email to VOTE for the release; the vote is now closed. The vote passes with Sixteen(16) +1 votes & no 0 vote & no -1 vote. Here are the vote details: Five +1 votes from the following PMC members: - Abhay Kulkarni - Madhan Neethiraj - Ramesh Mani - Selvamohan Neethiraj - Velmurugan Periasamy Eleven +1 votes from the following committers/contributors: - Abhishek Kumar - Dhaval Rajapara - Kishor Gollapalliwar - Mahesh Bandal - Mehul Parikh - Mugdha Varadkar - Pradeep Agrawal - Rakesh Gupta - Sanket Shelar - Subhrat Chaudhary - Vishal Suvagia Voting thread: https://lists.apache.org/thread/dx965jh42d21o3957y0n5p7q520jltc6 I will begin the process of publishing the release artifacts for Apache Ranger 2.5.0. Regard, Bhavik Patel +91-7208744109
Re: [VOTE] Release Apache Ranger version 2.5.0 - RC4
Hello Rangers, Thanks for taking your active participation in verify, giving the feedback and voting on Apache Ranger 2.5.0 release candidate #4. More than 72 hours have passed since the email to VOTE for the release; the vote is now closed. The vote passes with Sixteen(16) +1 votes & no 0 vote & no -1 vote. Here are the vote details: Five +1 votes from the following PMC members: - Abhay Kulkarni - Madhan Neethiraj - Ramesh Mani - Selvamohan Neethiraj - Velmurugan Periasamy Eleven +1 votes from the following committers/contributors: - Abhishek Kumar - Dhaval Rajapara - Kishor Gollapalliwar - Mahesh Bandal - Mehul Parikh - Mugdha Varadkar - Pradeep Agrawal - Rakesh Gupta - Sanket Shelar - Subhrat Chaudhary - Vishal Suvagia Voting thread: https://lists.apache.org/thread/dx965jh42d21o3957y0n5p7q520jltc6 I will begin the process of publishing the release artifacts for Apache Ranger 2.5.0. Regard, Bhavik Patel +91-7208744109 On Tue, Aug 6, 2024 at 8:39 PM Subhrat Chaudhary wrote: > Hi team, > +1 for Ranger 2.5.0 RC4 release > Following validations done for Ranger 2.5.0:1. All junits are passing. > 2. On local installation, ranger is up and running.3. Validated CRUD > operations for user/group/roles and policies. > Thanks & Regards,Subhrat Chaudhary > > > On Tuesday, August 6, 2024 at 08:25:41 PM GMT+5:30, Kishor > Gollapalliwar wrote: > > +1 for Ranger 2.5.0 RC4 release. > > I have performed the following validations. > - build with unit tests > - installation and start of ranger-admin > - CRUD operation of service, policy, user group & roles, security zone > > Thanks Bhavik for driving Apache Ranger 2.5.0 release. > > Thanks, > Kishor > > On Tue, Aug 6, 2024 at 8:07 PM Mahesh Bandal > wrote: > > > Hi Bhavik, > > > > Thank you for publishing the Apache Ranger 2.5.0 release candidate #4. > > Voting +1 for Ranger 2.5.0 RC4 release. > > > > I have performed the following validations. > > > >- build with unit tests > >- installation and start of ranger-admin > >- CRUD operation of service, policy, user group & roles, security zone > > > > > > Thanks and regards, > > -Mahesh Bandal. > > +91-9920370380 > > > > On Fri, Aug 2, 2024 at 9:52 PM Bhavik Patel > > wrote: > > > > > Hello Rangers, > > > > > > > > > Apache Ranger 2.5.0 release candidate #4 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) > > > > > > > > > List of all issues addressed in this release: > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc > > > > > > Git tag for the release: > > > https://github.com/apache/ranger/tree/release-2.5.0-rc4 > > > Sources for the release: > > > > > > > > > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz > > > > > > Source release verification: > > > PGP Signature: > > > > > > > > > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.asc > > > SHA256 > > > < > > > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.ascSHA256 > > > > > > Hash: > > > > > > > > > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.sha256 > > > SHA512 > > > < > > > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.sha256SHA512 > > > > > > Hash: > > > > > > > > > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.sha512 > > > > > > Release notes(2.5.0-rc4) : > > > > > > > > > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/Apache%20Ranger%202.5.0%20Release%20Notes > > > > > > > > > Regard, > > > Bhavik Patel > > > +91-7208744109 > > > > > > > > -- > Thanks & Regards, > *Kishor Golapelliwar,* > The ability to convert ideas to things is the secret to outward success. >
[VOTE] Release Apache Ranger version 2.5.0 - RC4
Hello Rangers, Apache Ranger 2.5.0 release candidate #4 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) List of all issues addressed in this release: https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc Git tag for the release: https://github.com/apache/ranger/tree/release-2.5.0-rc4 Sources for the release: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz Source release verification: PGP Signature: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.asc SHA256 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.sha256 SHA512 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/apache-ranger-2.5.0.tar.gz.sha512 Release notes(2.5.0-rc4) : https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc4/Apache%20Ranger%202.5.0%20Release%20Notes Regard, Bhavik Patel +91-7208744109
[jira] [Commented] (RANGER-4884) updated dependent library version: hadoop, aws sdk, avro, snakeyaml
[ https://issues.apache.org/jira/browse/RANGER-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870504#comment-17870504 ] Bhavik Patel commented on RANGER-4884: -- commit link for ranger-2.5 branch : https://github.com/apache/ranger/commit/8c6b787d8198274835765644ddb9b5a0269c9d13 > updated dependent library version: hadoop, aws sdk, avro, snakeyaml > --- > > Key: RANGER-4884 > URL: https://issues.apache.org/jira/browse/RANGER-4884 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Madhan Neethiraj >Assignee: Grzegorz Kokosinski >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > This Jira tracks following pull requests by [~kokosing]: > # [#363: Update hadoop to 3.3.4|https://github.com/apache/ranger/pull/363] > # [#364: Exclude all io.netty from hive-agent > tests|https://github.com/apache/ranger/pull/364] > # [#365: Update AWS SDK to > 1.12.765|https://github.com/apache/ranger/pull/365] > # [#366: Exclude avro dependency|https://github.com/apache/ranger/pull/366] > # [#367: Exclude snakeyaml dependency to avoid > CVEs|https://github.com/apache/ranger/pull/367] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4884) updated dependent library version: hadoop, aws sdk, avro, snakeyaml
[ https://issues.apache.org/jira/browse/RANGER-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4884: - Fix Version/s: 2.5.0 > updated dependent library version: hadoop, aws sdk, avro, snakeyaml > --- > > Key: RANGER-4884 > URL: https://issues.apache.org/jira/browse/RANGER-4884 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Madhan Neethiraj >Assignee: Grzegorz Kokosinski >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > This Jira tracks following pull requests by [~kokosing]: > # [#363: Update hadoop to 3.3.4|https://github.com/apache/ranger/pull/363] > # [#364: Exclude all io.netty from hive-agent > tests|https://github.com/apache/ranger/pull/364] > # [#365: Update AWS SDK to > 1.12.765|https://github.com/apache/ranger/pull/365] > # [#366: Exclude avro dependency|https://github.com/apache/ranger/pull/366] > # [#367: Exclude snakeyaml dependency to avoid > CVEs|https://github.com/apache/ranger/pull/367] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4877) Upgrade requireJS to 2.3.6 to 2.3.7.
[ https://issues.apache.org/jira/browse/RANGER-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4877: - Fix Version/s: 3.0.0 2.5.0 > Upgrade requireJS to 2.3.6 to 2.3.7. > > > Key: RANGER-4877 > URL: https://issues.apache.org/jira/browse/RANGER-4877 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0, 2.5.0 > > > Upgrade requireJS to 2.3.6 to 2.3.7. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4877) Upgrade requireJS to 2.3.6 to 2.3.7.
[ https://issues.apache.org/jira/browse/RANGER-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel resolved RANGER-4877. -- Resolution: Fixed > Upgrade requireJS to 2.3.6 to 2.3.7. > > > Key: RANGER-4877 > URL: https://issues.apache.org/jira/browse/RANGER-4877 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0, 2.5.0 > > > Upgrade requireJS to 2.3.6 to 2.3.7. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4877) Upgrade requireJS to 2.3.6 to 2.3.7.
[ https://issues.apache.org/jira/browse/RANGER-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4877: - Issue Type: Improvement (was: Bug) > Upgrade requireJS to 2.3.6 to 2.3.7. > > > Key: RANGER-4877 > URL: https://issues.apache.org/jira/browse/RANGER-4877 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0, 2.5.0 > > > Upgrade requireJS to 2.3.6 to 2.3.7. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4877) Upgrade requireJS to 2.3.6 to 2.3.7.
[ https://issues.apache.org/jira/browse/RANGER-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4877: - Affects Version/s: 3.0.0 2.5.0 > Upgrade requireJS to 2.3.6 to 2.3.7. > > > Key: RANGER-4877 > URL: https://issues.apache.org/jira/browse/RANGER-4877 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0, 2.5.0 > > > Upgrade requireJS to 2.3.6 to 2.3.7. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4877) Upgrade requireJS to 2.3.6 to 2.3.7.
[ https://issues.apache.org/jira/browse/RANGER-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870501#comment-17870501 ] Bhavik Patel commented on RANGER-4877: -- master branch commit : https://github.com/apache/ranger/commit/286066a86a1f80d3731d81473c423795d8102ae0 ranger-2.5 branch commit : https://github.com/apache/ranger/commit/f3e2a44f0d7f80be4eed95b456f5066089a88891 > Upgrade requireJS to 2.3.6 to 2.3.7. > > > Key: RANGER-4877 > URL: https://issues.apache.org/jira/browse/RANGER-4877 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > Upgrade requireJS to 2.3.6 to 2.3.7. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 75124: RANGER-4877 : Upgrade requireJS to 2.3.6 to 2.3.7.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75124/#review226765 --- Ship it! Ship It! - bhavik patel On Aug. 2, 2024, 12:13 p.m., Dhaval Rajpara wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/75124/ > --- > > (Updated Aug. 2, 2024, 12:13 p.m.) > > > Review request for ranger, bhavik patel, Brijesh Bhalala, Dineshkumar Yadav, > Madhan Neethiraj, and Mugdha Varadkar. > > > Bugs: RANGER-4877 > https://issues.apache.org/jira/browse/RANGER-4877 > > > Repository: ranger > > > Description > --- > > Upgrade requireJS to 2.3.6 to 2.3.7. > > > Diffs > - > > security-admin/src/main/webapp/libs/bower/requirejs/js/require.js 662573819 > security-admin/src/main/webapp/package-lock.json f7a72833f > security-admin/src/main/webapp/package.json 9f2274445 > > > Diff: https://reviews.apache.org/r/75124/diff/2/ > > > Testing > --- > > Tested rander admin build with this patch. > And checked Crud Opration for services / policies / Security Zone/ > users/groups/roles > > > Thanks, > > Dhaval Rajpara > >
[jira] [Commented] (RANGER-4877) Upgrade requireJS to 2.3.6 to 2.3.7.
[ https://issues.apache.org/jira/browse/RANGER-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870404#comment-17870404 ] Bhavik Patel commented on RANGER-4877: -- What is the ETA? > Upgrade requireJS to 2.3.6 to 2.3.7. > > > Key: RANGER-4877 > URL: https://issues.apache.org/jira/browse/RANGER-4877 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > > Upgrade requireJS to 2.3.6 to 2.3.7. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4885) upgrade from 2.4.0 to 2.5.0 fails due to missing column
[
https://issues.apache.org/jira/browse/RANGER-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870375#comment-17870375
]
Bhavik Patel edited comment on RANGER-4885 at 8/2/24 6:06 AM:
--
Thanks [~madhan] for working on the release blocker.
Commit link for ranger-2.5 branch:
https://github.com/apache/ranger/commit/2bb5644dcf2e4ff00e76a2d320a705785de6ce6b
was (Author: bpatel):
Commit link for ranger-2.5 branch:
https://github.com/apache/ranger/commit/2bb5644dcf2e4ff00e76a2d320a705785de6ce6b
> upgrade from 2.4.0 to 2.5.0 fails due to missing column
> ---
>
> Key: RANGER-4885
> URL: https://issues.apache.org/jira/browse/RANGER-4885
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.5.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: RANGER-4885.patch
>
>
> Apache Ranger 2.5.0 upgraded from 2.4.0 fails during startup with the
> following error:
> {noformat}
> 2024-08-01 18:24:05,193 [I] java patch
> PatchForOzoneServiceDefConfigUpdate_J10051 is being applied..
> log4j:WARN No appenders could be found for logger
> (org.apache.ranger.patch.PatchForOzoneServiceDefConfigUpdate_J10051).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> [EL Warning]: metadata: 2024-08-01
> 18:24:06.907--ServerSession(1578026015)--You have specified multiple ids for
> the entity class [org.apache.ranger.entity.view.VXXPrincipal] without
> specifying an @IdClass. By doing this you may lose the ability to find by
> identity, distributed cache support etc. Note: You may however use
> EntityManager find operations by passing a list of primary key fields. Else,
> you will have to use JPQL queries to read your entities. For other id options
> see @PrimaryKey.
> [EL Warning]: 2024-08-01 18:24:07.888--UnitOfWork(712753515)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: column
> "category" does not exist
> Position: 25
> Error Code: 0
> Call: SELECT id, ADDED_BY_ID, category, CREATE_TIME, datamask_options,
> def_id, item_id, label, name, sort_order, rb_key_label, rowfilter_options,
> UPDATE_TIME, UPD_BY_ID FROM x_access_type_def WHERE (def_id = ?) ORDER BY
> sort_order
> bind => [1 parameter bound]
> Query: ReadAllQuery(name="XXAccessTypeDef.findByServiceDefId"
> referenceClass=XXAccessTypeDef sql="SELECT id, ADDED_BY_ID, category,
> CREATE_TIME, datamask_options, def_id, item_id, label, name, sort_order,
> rb_key_label, rowfilter_options, UPDATE_TIME, UPD_BY_ID FROM
> x_access_type_def WHERE (def_id = ?) ORDER BY sort_order")
> [EL Warning]: 2024-08-01 18:24:07.893--UnitOfWork(712753515)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: current
> transaction is aborted, commands ignored until end of transaction block
> Error Code: 0
> ...
> ...
> [EL Warning]: 2024-08-01 18:24:08.194--UnitOfWork(1608894091)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: column
> "category" does not exist
> Position: 25
> Error Code: 0
> Call: SELECT id, ADDED_BY_ID, category, CREATE_TIME, datamask_options,
> def_id, item_id, label, name, sort_order, rb_key_label, rowfilter_options,
> UPDATE_TIME, UPD_BY_ID FROM x_access_type_def WHERE (def_id = ?) ORDER BY
> sort_order
> bind => [1 parameter bound]
> Query: ReadAllQuery(name="XXAccessTypeDef.findByServiceDefId"
> referenceClass=XXAccessTypeDef sql="SELECT id, ADDED_BY_ID, category,
> CREATE_TIME, datamask_options, def_id, item_id, label, name, sort_order,
> rb_key_label, rowfilter_options, UPDATE_TIME, UPD_BY_ID FROM
> x_access_type_def WHERE (def_id = ?) ORDER BY sort_order")
> 2024-08-01 18:24:08,227 [JISQL] /usr/lib/jvm/java-8-openjdk-arm64/bin/java
> -cp /usr/share/java/postgresql.jar:/opt/ranger/ranger-2.5.0-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver postgres
[jira] [Commented] (RANGER-4885) upgrade from 2.4.0 to 2.5.0 fails due to missing column
[
https://issues.apache.org/jira/browse/RANGER-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870375#comment-17870375
]
Bhavik Patel commented on RANGER-4885:
--
Commit link for ranger-2.5 branch:
https://github.com/apache/ranger/commit/2bb5644dcf2e4ff00e76a2d320a705785de6ce6b
> upgrade from 2.4.0 to 2.5.0 fails due to missing column
> ---
>
> Key: RANGER-4885
> URL: https://issues.apache.org/jira/browse/RANGER-4885
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.5.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: RANGER-4885.patch
>
>
> Apache Ranger 2.5.0 upgraded from 2.4.0 fails during startup with the
> following error:
> {noformat}
> 2024-08-01 18:24:05,193 [I] java patch
> PatchForOzoneServiceDefConfigUpdate_J10051 is being applied..
> log4j:WARN No appenders could be found for logger
> (org.apache.ranger.patch.PatchForOzoneServiceDefConfigUpdate_J10051).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> [EL Warning]: metadata: 2024-08-01
> 18:24:06.907--ServerSession(1578026015)--You have specified multiple ids for
> the entity class [org.apache.ranger.entity.view.VXXPrincipal] without
> specifying an @IdClass. By doing this you may lose the ability to find by
> identity, distributed cache support etc. Note: You may however use
> EntityManager find operations by passing a list of primary key fields. Else,
> you will have to use JPQL queries to read your entities. For other id options
> see @PrimaryKey.
> [EL Warning]: 2024-08-01 18:24:07.888--UnitOfWork(712753515)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: column
> "category" does not exist
> Position: 25
> Error Code: 0
> Call: SELECT id, ADDED_BY_ID, category, CREATE_TIME, datamask_options,
> def_id, item_id, label, name, sort_order, rb_key_label, rowfilter_options,
> UPDATE_TIME, UPD_BY_ID FROM x_access_type_def WHERE (def_id = ?) ORDER BY
> sort_order
> bind => [1 parameter bound]
> Query: ReadAllQuery(name="XXAccessTypeDef.findByServiceDefId"
> referenceClass=XXAccessTypeDef sql="SELECT id, ADDED_BY_ID, category,
> CREATE_TIME, datamask_options, def_id, item_id, label, name, sort_order,
> rb_key_label, rowfilter_options, UPDATE_TIME, UPD_BY_ID FROM
> x_access_type_def WHERE (def_id = ?) ORDER BY sort_order")
> [EL Warning]: 2024-08-01 18:24:07.893--UnitOfWork(712753515)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: current
> transaction is aborted, commands ignored until end of transaction block
> Error Code: 0
> ...
> ...
> [EL Warning]: 2024-08-01 18:24:08.194--UnitOfWork(1608894091)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services -
> 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: column
> "category" does not exist
> Position: 25
> Error Code: 0
> Call: SELECT id, ADDED_BY_ID, category, CREATE_TIME, datamask_options,
> def_id, item_id, label, name, sort_order, rb_key_label, rowfilter_options,
> UPDATE_TIME, UPD_BY_ID FROM x_access_type_def WHERE (def_id = ?) ORDER BY
> sort_order
> bind => [1 parameter bound]
> Query: ReadAllQuery(name="XXAccessTypeDef.findByServiceDefId"
> referenceClass=XXAccessTypeDef sql="SELECT id, ADDED_BY_ID, category,
> CREATE_TIME, datamask_options, def_id, item_id, label, name, sort_order,
> rb_key_label, rowfilter_options, UPDATE_TIME, UPD_BY_ID FROM
> x_access_type_def WHERE (def_id = ?) ORDER BY sort_order")
> 2024-08-01 18:24:08,227 [JISQL] /usr/lib/jvm/java-8-openjdk-arm64/bin/java
> -cp /usr/share/java/postgresql.jar:/opt/ranger/ranger-2.5.0-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver postgresql -cstring
> jdbc:postgresql://ranger-db/ranger -u rangeradmin -p '' -noheader
> -trim -c \; -query "delete from x_db_version_h where version = 'J10051' and
> active = 'N' and updated_by='ranger.example.com';"
> 2024-08-01 18:24:08,308 [E] applying java patch
> PatchForOzoneServiceDefConfigUpdate_J10051 failed
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4882) update dependent library version: fasterxml.jackson, jersey
[ https://issues.apache.org/jira/browse/RANGER-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4882: - Fix Version/s: 2.5.0 > update dependent library version: fasterxml.jackson, jersey > --- > > Key: RANGER-4882 > URL: https://issues.apache.org/jira/browse/RANGER-4882 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Attachments: RANGER-4882.patch > > > Update version of following dependent libraries to the latest available > version: > * fasterxml.jackson: 2.17.0 => 2.17.2 > * jersey: 1.19.3 => 1.19.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4882) update dependent library version: fasterxml.jackson, jersey
[ https://issues.apache.org/jira/browse/RANGER-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870372#comment-17870372 ] Bhavik Patel commented on RANGER-4882: -- Commit link for ranger-2.5 branch : https://github.com/apache/ranger/commit/1e26674940ca11aff0c0595905e033eaffb7f520 > update dependent library version: fasterxml.jackson, jersey > --- > > Key: RANGER-4882 > URL: https://issues.apache.org/jira/browse/RANGER-4882 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4882.patch > > > Update version of following dependent libraries to the latest available > version: > * fasterxml.jackson: 2.17.0 => 2.17.2 > * jersey: 1.19.3 => 1.19.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 75136: RANGER-4885: added db patches to update schema during upgrade
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75136/#review226762 --- Ship it! Ship It! - bhavik patel On Aug. 2, 2024, 1:33 a.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/75136/ > --- > > (Updated Aug. 2, 2024, 1:33 a.m.) > > > Review request for ranger, Anand Nadar, Asit Vadhavkar, bhavik patel, Kishor > Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Mugdha Varadkar, Pradeep > Agrawal, Ramesh Mani, Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan > Periasamy. > > > Bugs: RANGER-4885 > https://issues.apache.org/jira/browse/RANGER-4885 > > > Repository: ranger > > > Description > --- > > - added DB patches to add following in the database schema during upgrade > -- view: vx_principal > -- column: x_access_type_def.category > -- column: x_security_zon.gz_jsondata > > > Diffs > - > > security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql > deecac27e > security-admin/db/mysql/patches/068-create-view-principal.sql PRE-CREATION > security-admin/db/mysql/patches/069-add-gz_json_x_security_zone.sql > PRE-CREATION > security-admin/db/mysql/patches/072-alter-x_access_type_def.sql > PRE-CREATION > security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql > aa64b48e5 > security-admin/db/oracle/patches/068-create-view-principal.sql PRE-CREATION > security-admin/db/oracle/patches/069-add-gz_json_x_security_zone.sql > PRE-CREATION > security-admin/db/oracle/patches/072-alter-x_access_type_def.sql > PRE-CREATION > security-admin/db/oracle/patches/077-create-x_trx_log_v2.sql > security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql > 2eec8aafd > security-admin/db/postgres/patches/068-create-view-principal.sql > PRE-CREATION > security-admin/db/postgres/patches/069-add-gz_json_x_security_zone.sql > PRE-CREATION > security-admin/db/postgres/patches/072-alter-x_access_type_def.sql > PRE-CREATION > > security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql > 1d276fb85 > security-admin/db/sqlanywhere/patches/067-create-x_trx_log_v2.sql > security-admin/db/sqlanywhere/patches/068-create-view-principal.sql > PRE-CREATION > security-admin/db/sqlanywhere/patches/069-add-gz_json_x_security_zone.sql > PRE-CREATION > security-admin/db/sqlanywhere/patches/072-alter-x_access_type_def.sql > PRE-CREATION > security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql > c49d4c09c > security-admin/db/sqlserver/patches/067-create-x_trx_log_v2.sql > security-admin/db/sqlserver/patches/068-create-view-principal.sql > PRE-CREATION > security-admin/db/sqlserver/patches/069-add-gz_json_x_security_zone.sql > PRE-CREATION > security-admin/db/sqlserver/patches/072-alter-x_access_type_def.sql > PRE-CREATION > > > Diff: https://reviews.apache.org/r/75136/diff/1/ > > > Testing > --- > > - verified build with unit tests complete successfully > - verified upgrading from 2.4.0 to 2.5.0, with Postgres and MySQL databases > - verified fresh install of 2.5.0, with Postgres and MySQL databases > > > Thanks, > > Madhan Neethiraj > >
[jira] [Commented] (RANGER-4884) updated dependent library version: hadoop, aws sdk, avro, snakeyaml
[ https://issues.apache.org/jira/browse/RANGER-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870182#comment-17870182 ] Bhavik Patel commented on RANGER-4884: -- Thanks [~kokosing] for fixing the CVE's. * Hadoop: As Madhan indicated, versions 3.3.5 and 3.3.6 of Hadoop have been available for some time. Is there a specific reason we have not updated to the latest version? * Avro: Can you also update the assembly packaging file, for example: https://github.com/apache/ranger/blob/master/distro/src/main/assembly/kms.xml? * snakeyaml: I believe this is used in runtime when audit to Elasticsearch (destination) is enabled. Have you validated this functionality? > updated dependent library version: hadoop, aws sdk, avro, snakeyaml > --- > > Key: RANGER-4884 > URL: https://issues.apache.org/jira/browse/RANGER-4884 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Madhan Neethiraj >Assignee: Grzegorz Kokosinski >Priority: Major > Fix For: 3.0.0 > > > This Jira tracks following pull requests by [~kokosing]: > # [#363: Update hadoop to 3.3.4|https://github.com/apache/ranger/pull/363] > # [#364: Exclude all io.netty from hive-agent > tests|https://github.com/apache/ranger/pull/364] > # [#365: Update AWS SDK to > 1.12.765|https://github.com/apache/ranger/pull/365] > # [#366: Exclude avro dependency|https://github.com/apache/ranger/pull/366] > # [#367: Exclude snakeyaml dependency to avoid > CVEs|https://github.com/apache/ranger/pull/367] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4878) Upgrade webpack version to latest 5.93.0
[ https://issues.apache.org/jira/browse/RANGER-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4878: - Fix Version/s: 2.5.0 > Upgrade webpack version to latest 5.93.0 > > > Key: RANGER-4878 > URL: https://issues.apache.org/jira/browse/RANGER-4878 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Attachments: 0001-RANGER-4878-master.patch, > 0001-RANGER-4878-ranger-2.5.patch > > > Need to update the webpack version to latest 5.93.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[VOTE] Release Apache Ranger version 2.5.0 - RC3
Hello Rangers, Kindly ignore the previous email for voting. Apache Ranger 2.5.0 release candidate #3 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) List of all issues addressed in this release: https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc Git tag for the release: https://github.com/apache/ranger/tree/release-2.5.0-rc3 Sources for the release: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc3/apache-ranger-2.5.0.tar.gz Source release verification: PGP Signature: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc3/apache-ranger-2.5.0.tar.gz.asc SHA256 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc3/apache-ranger-2.5.0.tar.gz.sha256 SHA512 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc3/apache-ranger-2.5.0.tar.gz.sha512 Release notes(2.5.0-rc3) : https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc3/Apache%20Ranger%202.5.0%20Release%20Notes Regard, Bhavik Patel +91-7208744109
[VOTE] Release Apache Ranger version 2.5.0 - RC3
Hello Rangers, Apache Ranger 2.5.0 release candidate #3 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) List of all issues addressed in this release: https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc Git tag for the release: https://github.com/apache/ranger/tree/release-2.5.0-rc3 Sources for the release: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc3/apache-ranger-2.5.0.tar.gz Source release verification: PGP Signature: https://home.apache.org/~bpatel/2.5.0-rc3/apache-ranger-2.5.0.tar.gz.asc SHA256 Hash: https://home.apache.org/~bpatel/2.5.0-rc3/apache-ranger-2.5.0.tar.gz.sha256 SHA512 Hash: https://home.apache.org/~bpatel/2.5.0-rc3/apache-ranger-2.5.0.tar.gz.sha512 Release notes(2.5.0-rc3) : https://home.apache.org/~bpatel/2.5.0-rc3/Apache%20Ranger%202.5.0%20Release%20Notes Regard, Bhavik Patel +91-7208744109
[jira] [Updated] (RANGER-4878) Upgrade webpack version to latest 5.93.0
[ https://issues.apache.org/jira/browse/RANGER-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4878: - Issue Type: Improvement (was: Bug) > Upgrade webpack version to latest 5.93.0 > > > Key: RANGER-4878 > URL: https://issues.apache.org/jira/browse/RANGER-4878 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4878-master.patch, > 0001-RANGER-4878-ranger-2.5.patch > > > Need to update the webpack version to latest 5.93.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4880) Change pom version from 2.5.0-SNAPSHOT to 2.5.0
[ https://issues.apache.org/jira/browse/RANGER-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869724#comment-17869724 ] Bhavik Patel commented on RANGER-4880: -- Commit link : https://github.com/apache/ranger/commit/79f839292f6f1b439409074c61200f75911dcd12 > Change pom version from 2.5.0-SNAPSHOT to 2.5.0 > --- > > Key: RANGER-4880 > URL: https://issues.apache.org/jira/browse/RANGER-4880 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > > Update pom version from 2.5.0-SNAPSHOT to 2.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 75129: RANGER-4880: Change pom version from 2.5.0-SNAPSHOT to 2.5.0
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75129/ --- Review request for ranger, madhan, Madhan Neethiraj, Selvamohan Neethiraj, and Velmurugan Periasamy. Bugs: RANGER-4880 https://issues.apache.org/jira/browse/RANGER-4880 Repository: ranger Description --- Change pom version from 2.5.0-SNAPSHOT to 2.5.0 Diffs - agents-audit/pom.xml e8f5c20b8 agents-common/pom.xml 26d4ca633 agents-cred/pom.xml b8950319a agents-installer/pom.xml 3c184cfe7 credentialbuilder/pom.xml 5317df429 dev-support/ranger-docker/.env dc03dba8a distro/pom.xml fae6effe9 embeddedwebserver/pom.xml fb8c075ac hbase-agent/pom.xml f5c87d195 hdfs-agent/pom.xml af1a12188 hive-agent/pom.xml 6380f1fc0 intg/pom.xml 785fd5bed jisql/pom.xml 95cf73471 kms/pom.xml 9d4e601fc knox-agent/pom.xml b3ae482e8 plugin-atlas/pom.xml 8cf822d93 plugin-elasticsearch/pom.xml fdd3e0536 plugin-kafka/pom.xml 0214f6515 plugin-kms/pom.xml 9ee9ba32a plugin-kudu/pom.xml 03987a0a2 plugin-kylin/pom.xml 1288f9b9f plugin-nestedstructure/pom.xml 7dfef849a plugin-nifi-registry/pom.xml 05d7f0fb6 plugin-nifi/pom.xml 949d64676 plugin-ozone/pom.xml a18b87f3e plugin-presto/pom.xml da113e9a1 plugin-schema-registry/pom.xml ba2831472 plugin-solr/pom.xml 1905b9600 plugin-sqoop/pom.xml 35cd97446 plugin-trino/pom.xml c00909021 plugin-yarn/pom.xml cfa4df078 pom.xml a964d045e ranger-atlas-plugin-shim/pom.xml b674ac8b9 ranger-authn/pom.xml 807d413db ranger-common-ha/pom.xml 4482c7f61 ranger-elasticsearch-plugin-shim/pom.xml 59eef3e85 ranger-examples/conditions-enrichers/pom.xml d557f45ad ranger-examples/distro/pom.xml 7c8601d11 ranger-examples/plugin-sampleapp/pom.xml 63febb16b ranger-examples/pom.xml 8dce09861 ranger-examples/sample-client/pom.xml c798db435 ranger-examples/sampleapp/pom.xml 5dcfb6968 ranger-hbase-plugin-shim/pom.xml efc59424c ranger-hdfs-plugin-shim/pom.xml 70ba342e8 ranger-hive-plugin-shim/pom.xml e22c6b671 ranger-kafka-plugin-shim/pom.xml 745ac53d3 ranger-kms-plugin-shim/pom.xml 4b05daec8 ranger-knox-plugin-shim/pom.xml 100574490 ranger-kylin-plugin-shim/pom.xml 46e3e5722 ranger-metrics/pom.xml 630ef0673 ranger-ozone-plugin-shim/pom.xml e2d66876d ranger-plugin-classloader/pom.xml 4832b8afe ranger-presto-plugin-shim/pom.xml bf93fe463 ranger-solr-plugin-shim/pom.xml 295a7d97b ranger-sqoop-plugin-shim/pom.xml 95f16a8fd ranger-storm-plugin-shim/pom.xml bac577d57 ranger-tools/pom.xml 14c3d56c9 ranger-util/pom.xml 4f5171a77 ranger-yarn-plugin-shim/pom.xml b7f87aece security-admin/pom.xml 19ee9fac0 storm-agent/pom.xml fab962ff0 tagsync/pom.xml 225223cf9 ugsync-util/pom.xml 2639b28a8 ugsync/ldapconfigchecktool/ldapconfigcheck/pom.xml 2366ab7ec ugsync/pom.xml 6822bca2f unixauthclient/pom.xml b62659883 unixauthnative/pom.xml 2ca4dfe0e unixauthpam/pom.xml 8ecebbdbb unixauthservice/pom.xml 594a8934b Diff: https://reviews.apache.org/r/75129/diff/1/ Testing --- Thanks, bhavik patel
[jira] [Created] (RANGER-4880) Change pom version from 2.5.0-SNAPSHOT to 2.5.0
Bhavik Patel created RANGER-4880: Summary: Change pom version from 2.5.0-SNAPSHOT to 2.5.0 Key: RANGER-4880 URL: https://issues.apache.org/jira/browse/RANGER-4880 Project: Ranger Issue Type: Sub-task Components: Ranger Affects Versions: 2.5.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Update pom version from 2.5.0-SNAPSHOT to 2.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[VOTE] Release Apache Ranger version 2.5.0 - RC2
Apache Ranger 2.5.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) List of all issues addressed in this release: https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc Git tag for the release: https://github.com/apache/ranger/tree/release-2.5.0-rc2 Sources for the release: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc2/apache-ranger-2.5.0.tar.gz Source release verification: PGP Signature: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc2/apache-ranger-2.5.0.tar.gz.asc SHA256 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc2/apache-ranger-2.5.0.tar.gz.sha256 SHA512 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc2/apache-ranger-2.5.0.tar.gz.sha512 Release notes(2.5.0-rc2) : https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc2/Apache%20Ranger%202.5.0%20Release%20Notes Regard, Bhavik Patel +91-7208744109
[Important] Kindly do not commit anything on ranger-2.5 branch
Hello Ranger, Kindly do not commit anything on ranger-2.5 branch as I'm preparing for release-candidate #2. On top of RC1 we have included three Jira's RANGER-4561, RANGER-4873 and RANGER-4874. Regard, Bhavik Patel +91-7208744109
Re: Review Request 75123: RANGER-4874: fix for AbstractMethodError: javax.ws.rs.core.Response.getStatusInfo()Ljavax/ws/rs/core/Response$StatusType;
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75123/#review226738 --- Ship it! Ship It! - bhavik patel On July 30, 2024, 4:47 a.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/75123/ > --- > > (Updated July 30, 2024, 4:47 a.m.) > > > Review request for ranger, Abhishek Kumar, Fateh Singh, Kishor > Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Mugdha Varadkar, Pradeep > Agrawal, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4874 > https://issues.apache.org/jira/browse/RANGER-4874 > > > Repository: ranger > > > Description > --- > > - version of javax.ws.rs included in jersey-bundle is older compared to the > javax.ws.rs-api-2.1.1, which resulted in AbstractMethodError > - to address this error, removed javax.ws.rs-api-2.1.1 from > dependency/packaging > - jackson-jaxrs-json-provider requires class > javax.ws.rs.core.NoContentException, which is missing in jersey-bundle > - to address this issue, added class javax.ws.rs.core.NoContentException in > security-admin and kms modules > > > Diffs > - > > agents-audit/pom.xml b0e7bb92a > agents-common/pom.xml 02c4a2362 > agents-cred/pom.xml 6ed81be0b > credentialbuilder/pom.xml 6e5dc7c0c > distro/src/main/assembly/sample-client.xml dd01d1f47 > hbase-agent/pom.xml 1d214cdcc > hdfs-agent/pom.xml e51ec307d > kms/pom.xml 0003378a5 > kms/src/main/java/javax/ws/rs/core/NoContentException.java PRE-CREATION > knox-agent/pom.xml 9063fda2b > plugin-kafka/pom.xml bac40aac8 > plugin-ozone/pom.xml 7fa198f0a > plugin-schema-registry/pom.xml fa4f781bc > plugin-yarn/pom.xml c5263ecff > pom.xml bd5b69600 > ranger-authn/pom.xml 361a130f5 > ranger-common-ha/pom.xml b1fba9690 > ranger-examples/plugin-sampleapp/pom.xml 297cabeda > ranger-hdfs-plugin-shim/pom.xml fb4ecb631 > ranger-metrics/pom.xml c9b676460 > ranger-presto-plugin-shim/pom.xml 05d0c7fe8 > ranger-yarn-plugin-shim/pom.xml 83d3b67d6 > security-admin/pom.xml ddc7dfffd > security-admin/src/main/java/javax/ws/rs/core/NoContentException.java > PRE-CREATION > storm-agent/pom.xml 38f3f6a33 > ugsync/pom.xml 1240711f4 > > > Diff: https://reviews.apache.org/r/75123/diff/1/ > > > Testing > --- > > - verified that build with unit tests pass successfully > - verified that Ranger servers startup and initialize successfully > - verified that Ranger plugins install, initialize, enforce Ranger policies > and generate audit logs > - verified that Ranger server installation has only one library containing > javax.ws.rs.core.Response - jersey-bundle-1.19.3.jar > > > Thanks, > > Madhan Neethiraj > >
[jira] [Commented] (RANGER-4873) update zookeeper version from 3.5.5 to 3.9.2
[ https://issues.apache.org/jira/browse/RANGER-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869094#comment-17869094 ] Bhavik Patel commented on RANGER-4873: -- [~ksobolewsb] Have you validated the ranger-kms functionality? as Zookeeper 3.9.2 supports upgraded curator version > update zookeeper version from 3.5.5 to 3.9.2 > > > Key: RANGER-4873 > URL: https://issues.apache.org/jira/browse/RANGER-4873 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Krzysztof Sobolewski >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > This Jira tracks [pull request > #359|https://github.com/apache/ranger/pull/359]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release Apache Ranger version 2.5.0 - RC1
Thanks Madhan for the verification. I will update the release notes. Thanks, Bhavik Patel +91-7208744109 On Sat, 27 Jul 2024, 5:46 am Madhan Neethiraj, wrote: > Bhavik, > > > > Thank you for Apache Ranger 2.5.0 release candidate #1. > > > Verified hashes for apache-ranger-2.5.0.tar.gz > Verified the signature > Verified build with unit tests > Verified install and startup of Ranger servers: admin, usersync, tagsync, > kms > Verified install, policy enforcement and auditing of Ranger plugins: HDFS, > Hive, HBase, Kafka, Knox, KMS, YARN > > > Can you please regenerate the release notes, for the recent updates in > JIRA type (Bug/Improvement/Task/New Feature)? > > > > +1 for release candidate #1 > > > > Thanks, > > Madhan > > > > > > From: Bhavik Patel > Reply-To: "priv...@ranger.apache.org" > Date: Thursday, July 25, 2024 at 10:08 PM > To: "dev@ranger.apache.org" , " > priv...@ranger.apache.org" > Subject: [VOTE] Release Apache Ranger version 2.5.0 - RC1 > > > > Hello Rangers, > > > Apache Ranger 2.5.0 release candidate #1(a couple of blockers and > improvement changes are committed on top RC0) 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) > > > > > > List of all issues addressed in this release: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc > > > > Git tag for the release: > https://github.com/apache/ranger/commits/release-2.5.0-rc1 > > Sources for the release: > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz > > > > Source release verification: > PGP Signature: > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.asc > SHA256 > <https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.ascSHA256> > Hash: > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.sha256 > SHA512 > <https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.sha256SHA512> > Hash: > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.sha512 > > > > Release notes(2.5.0-rc1) : > https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/Apache%20Ranger%202.5.0%20Release%20notes > > > > > > Regard, > > Bhavik Patel > > +91-7208744109 > >
[VOTE] Release Apache Ranger version 2.5.0 - RC1
Hello Rangers, Apache Ranger 2.5.0 release candidate #1(a couple of blockers and improvement changes are committed on top RC0) 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) List of all issues addressed in this release: https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc Git tag for the release: https://github.com/apache/ranger/commits/release-2.5.0-rc1 <https://github.com/apache/ranger/commits/release-2.5.0-rc1> Sources for the release: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz Source release verification: PGP Signature: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.asc SHA256 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.sha256 SHA512 Hash: https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/apache-ranger-2.5.0.tar.gz.sha512 Release notes(2.5.0-rc1) : https://dist.apache.org/repos/dist/dev/ranger/2.5.0-rc1/Apache%20Ranger%202.5.0%20Release%20notes Regard, Bhavik Patel +91-7208744109
[VOTE] Apache Ranger 2.5.0 rc0
Hello Rangers, Apache Ranger 2.5.0 release candidate #0 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) List of all issues addressed in this release: https://issues.apache.org/jira/issues/?jql=project%20%3D%20RANGER%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.5.0%20ORDER%20BY%20key%20desc Git tag for the release: https://github.com/apache/ranger/commits/release-2.5.0-rc0 Sources for the release: http://home.apache.org/~bpatel/2.5.0-rc0/apache-ranger-2.5.0.tar.gz Source release verification: PGP Signature: http://home.apache.org/~bpatel/2.5.0-rc0/apache-ranger-2.5.0.tar.gz.asc SHA256 Hash: http://home.apache.org/~bpatel/2.5.0-rc0/apache-ranger-2.5.0.tar.gz.sha256 SHA512 Hash: http://home.apache.org/~bpatel/2.5.0-rc0/apache-ranger-2.5.0.tar.gz.sha512 Release notes(2.5.0-rc0) : http://home.apache.org/~bpatel/2.5.0-rc0/Apache%20Ranger%202.5.0%20Release%20notes Note: Currently, the source tarball has been uploaded to the " http://home.apache.org/~bpatel/ <http://home.apache.org/~bpatel/2.5.0-rc0/apache-ranger-2.5.0.tar.gz>" since I'm encountering an issue with uploading it to the SVN repository " https://dist.apache.org/repos/dist/dev/ranger/";. To address this, I'm collaborating with Velmurugan and Selva. Regard, Bhavik Patel +91-7208744109
[jira] [Updated] (RANGER-4819) Proposal to Upgrade All React.js Dependent Libraries
[ https://issues.apache.org/jira/browse/RANGER-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4819: - Fix Version/s: 2.5.0 > Proposal to Upgrade All React.js Dependent Libraries > - > > Key: RANGER-4819 > URL: https://issues.apache.org/jira/browse/RANGER-4819 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Fix For: 2.5.0 > > Attachments: > 0001-RANGER-4819-Proposal-to-Upgrade-All-React.js-Depende.patch, > 0001-RANGER-4819-ranger-2.5.patch > > > Upgrading all dependent libraries for React.js in our project. This will > ensure we are using the latest versions, improving security, performance, and > compatibility with new features. > # babel/traverse > # axios > # braces > # follow-redirects > # json5 > # loader-utils > # minimist > # moment > # terser > # webpack > # webpack-dev-middleware -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Apache Ranger 2.5.0 release
Hello Ragers, I have started preparing the build. Request to all the committers to not to push any code changes now. Note: Release candidate zero will be published with one open issue RANGER-4851, One the fix is available will release one more candidate so all the blockers(which we might observed in rc0) will be handled during this time. Regard, Bhavik Patel +91-7208744109 On Thu, Jul 18, 2024 at 9:23 PM Madhan Neethiraj wrote: > Bhavik - thank you for the summary. We are getting close to the first > release candidate. Hopefully by Friday this week or on Monday next week. > > RANGER-4804: the fix was reviewed and approved a while back. I will merge > this shortly today. > RANGER-4851: @Dineshkumar Yadav - can you please update ETA? > > Rangers - if you would like any critical item addressed in 2.5.0 release, > please make sure to have a JIRA in place with "Fix Version"=2.5.0 and > Priority= Blocker > > Thanks, > Madhan > > > > > On 7/16/24, 9:37 AM, "Bhavik Patel" bhavikpatel...@gmail.com>> wrote: > > > Hello Rangers, > > > Gn that we have two open major issues > https://issues.apache.org/jira/browse/RANGER-4804 < > https://issues.apache.org/jira/browse/RANGER-4804> and > https://issues.apache.org/jira/browse/RANGER-4851 < > https://issues.apache.org/jira/browse/RANGER-4851>, we plan to distribute > the > first release candidate for voting this thursday or friday. > > > > > Regard, > Bhavik Patel > +91-7208744109 > > > > > On Wed, Jul 10, 2024 at 3:47 PM Bhavik Patel <mailto:bhavikpatel...@gmail.com>> > wrote: > > > > Thanks Madhan. > > > > @Ranger community, > > > > Please review the following brief plan and let me know if you have any > comments: > > > > > > 1. 2024-07-31, Wed: tentative release date > > > > 2. 2022-07-12, Fri: release branch will be closed for commits. After > this date, commits will require approval from the PMCs > > > > 3. 2022-07-16, Tue: first release candidate out for vote > > > > 4. 2022-07-25, Thu: tentative vote completion. > > > > > > Looking forward to your help in making the 2.5.0 release as planned. > > > > > > Regard, > > Bhavik Patel > > +91-7208744109 > > > > > > On Wed, Jul 10, 2024 at 2:12 PM Madhan Neethiraj <mailto:mad...@apache.org>> > > wrote: > > > >> Bhavik, > >> > >> Thank you for volunteering to be the release manager. As suggested > >> earlier, let's target 2.5.0 release by end of this month. > >> > >> Thanks, > >> Madhan > >> > >> > >> > >> > >> On 7/9/24, 12:28 AM, "Bhavik Patel" bhavikpatel...@gmail.com> >> bhavikpatel...@gmail.com <mailto:bhavikpatel...@gmail.com>>> wrote: > >> > >> > >> Thank you, Madhan, for getting the ball rolling on the release of newer > >> version for Ranger. > >> > >> > >> I would like to lead the release activity for the Apache Ranger version > >> 2.5.0 and have created jira RANGER-4844 to monitor and follow up the > >> release activities. > >> > >> > >> > >> > >> Thanks, > >> Bhavik Patel > >> +91-7208744109 > >> > >> > >> > >> > >> > >> > >> On Fri, 28 Jun 2024, 6:11 am Madhan Neethiraj, <mailto:mad...@apache.org> > >> <mailto:mad...@apache.org <mailto:mad...@apache.org>>> wrote: > >> > >> > >> > Ranger community, > >> > > >> > > >> > > >> > It has been 15 months since the last release of Apache Ranger, 2.4.0. > >> > During this time, the community has added 500 commits with several > >> > improvements, fixes, and new features. I propose we start preparing > for > >> the > >> > release of Apache Ranger 2.5.0 to include all these enhancements by > end > >> of > >> > July 2024. > >> > > >> > > >> > > >> > The branch ranger-2.5.0 will be used for this release. If you would > like > >> > any improvement or fix to be included in this release, please ensure > the > >> > fix-version is set to 2.5.0 in JIRA. > >> > > >> > > >> > > >> > Here are few key improvements: > >> > New UI implemented using React, replacing Backbone UI > >> > Performance improvements in several modules > >> > HDFS plugin, user-store loading, admin audits storage, reduced plugin > >> > memory footprint > >> > HA support for user-sync and tag-sync services > >> > Introduction of Metrics API > >> > Security zone supports admin-roles and auditor-roles > >> > Option to use user-groups associations in Ranger during authorization > in > >> > plugins > >> > Support to grant time-bound accesses at policy-item level > >> > Python client API to manage users, groups, user-group associations > >> > Kafka authorizer updates for KIP-504 > >> > API to purge x_policy_export_audit, x_trx_log tables > >> > Docker setup for Trino configured with Ranger authorizer > >> > Dependent libraries version updates > >> > > >> > > >> > The Apache Ranger PMC would appreciate your contributions and feedback > >> in > >> > getting 2.5.0 release out. > >> > > >> > > >> > > >> > Thanks, > >> > > >> > Madhan > >> > > >> > Apache Ranger PMC Member > >> > > >> > > >> > >> > >> > >> > >> > > > > >
[jira] [Commented] (RANGER-4851) Upon editing an User we are seeing some discrepancy in its Audit Admin logs
[
https://issues.apache.org/jira/browse/RANGER-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867162#comment-17867162
]
Bhavik Patel commented on RANGER-4851:
--
[~dineshkumar-yadav] Can you kindly provide an update on this?
> Upon editing an User we are seeing some discrepancy in its Audit Admin logs
>
>
> Key: RANGER-4851
> URL: https://issues.apache.org/jira/browse/RANGER-4851
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.5.0
>Reporter: Vishal Bhavsar
>Assignee: Dineshkumar Yadav
>Priority: Major
> Attachments: 0001-RANGER-4851-intermediate-patch.patch,
> snapshot1.png, snapshot2.png, snapshot3.png, snapshot4.png
>
>
> Upon editing an User we are seeing some discrepancy in its Audit Admin logs
> in "ranger-2.5" branch.
> Steps to repro:
> # Create user (eg vbuser1) by entering all the details in user create form
> except Group.
> # Now edit the user and add any group (eg group1) to it and save.
> # In Audit Admin tab we would see 3 corresponding logs entry for the above
> edit operation. Refer snapshot1
> ## One log is of "User profile updated {*}vbuser1{*}" of Audit Type: User
> Profile, upon clicking on it the modal opens which has "User Details: " table
> empty. Refer snapshot2
> ## Second log is of "User updated {*}vbuser1{*}" of Audit Type: Ranger User,
> upon clicking on it the modal opens with below observation. Refer snapshot3
> ### here "User Details: " table shows Password getting updated even when we
> did not edit the password
> ### in "Group: " table we are seeing groups numerical value instead of its
> string name i.e group1.
> ## Third log is of Audit Type: XA Group of Users , upon clicking on it modal
> opens which is blank i.e no detail seen. Refer snapshot4
> Have attached snapshots for reference.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Apache Ranger 2.5.0 release
Hi Madhan, Yes, I'm planning to release first candidate tomorrow only, as next week I am not available. Also, I'm not able to add my public key svn repository and might not have permission to push the binaries to svn repository as well. Can you please help me on that. Thanks, Bhavik Patel +91-7208744109 On Thu, 18 Jul 2024, 9:23 pm Madhan Neethiraj, wrote: > Bhavik - thank you for the summary. We are getting close to the first > release candidate. Hopefully by Friday this week or on Monday next week. > > RANGER-4804: the fix was reviewed and approved a while back. I will merge > this shortly today. > RANGER-4851: @Dineshkumar Yadav - can you please update ETA? > > Rangers - if you would like any critical item addressed in 2.5.0 release, > please make sure to have a JIRA in place with "Fix Version"=2.5.0 and > Priority= Blocker > > Thanks, > Madhan > > > > > On 7/16/24, 9:37 AM, "Bhavik Patel" bhavikpatel...@gmail.com>> wrote: > > > Hello Rangers, > > > Gn that we have two open major issues > https://issues.apache.org/jira/browse/RANGER-4804 < > https://issues.apache.org/jira/browse/RANGER-4804> and > https://issues.apache.org/jira/browse/RANGER-4851 < > https://issues.apache.org/jira/browse/RANGER-4851>, we plan to distribute > the > first release candidate for voting this thursday or friday. > > > > > Regard, > Bhavik Patel > +91-7208744109 > > > > > On Wed, Jul 10, 2024 at 3:47 PM Bhavik Patel <mailto:bhavikpatel...@gmail.com>> > wrote: > > > > Thanks Madhan. > > > > @Ranger community, > > > > Please review the following brief plan and let me know if you have any > comments: > > > > > > 1. 2024-07-31, Wed: tentative release date > > > > 2. 2022-07-12, Fri: release branch will be closed for commits. After > this date, commits will require approval from the PMCs > > > > 3. 2022-07-16, Tue: first release candidate out for vote > > > > 4. 2022-07-25, Thu: tentative vote completion. > > > > > > Looking forward to your help in making the 2.5.0 release as planned. > > > > > > Regard, > > Bhavik Patel > > +91-7208744109 > > > > > > On Wed, Jul 10, 2024 at 2:12 PM Madhan Neethiraj <mailto:mad...@apache.org>> > > wrote: > > > >> Bhavik, > >> > >> Thank you for volunteering to be the release manager. As suggested > >> earlier, let's target 2.5.0 release by end of this month. > >> > >> Thanks, > >> Madhan > >> > >> > >> > >> > >> On 7/9/24, 12:28 AM, "Bhavik Patel" bhavikpatel...@gmail.com> >> bhavikpatel...@gmail.com <mailto:bhavikpatel...@gmail.com>>> wrote: > >> > >> > >> Thank you, Madhan, for getting the ball rolling on the release of newer > >> version for Ranger. > >> > >> > >> I would like to lead the release activity for the Apache Ranger version > >> 2.5.0 and have created jira RANGER-4844 to monitor and follow up the > >> release activities. > >> > >> > >> > >> > >> Thanks, > >> Bhavik Patel > >> +91-7208744109 > >> > >> > >> > >> > >> > >> > >> On Fri, 28 Jun 2024, 6:11 am Madhan Neethiraj, <mailto:mad...@apache.org> > >> <mailto:mad...@apache.org <mailto:mad...@apache.org>>> wrote: > >> > >> > >> > Ranger community, > >> > > >> > > >> > > >> > It has been 15 months since the last release of Apache Ranger, 2.4.0. > >> > During this time, the community has added 500 commits with several > >> > improvements, fixes, and new features. I propose we start preparing > for > >> the > >> > release of Apache Ranger 2.5.0 to include all these enhancements by > end > >> of > >> > July 2024. > >> > > >> > > >> > > >> > The branch ranger-2.5.0 will be used for this release. If you would > like > >> > any improvement or fix to be included in this release, please ensure > the > >> > fix-version is set to 2.5.0 in JIRA. > >> > > >> > > >> > > >> > Here are few key improvements: > >> > New UI implemented using React, replacing Backbone UI > >> > Performance improvements in several modules > >> > HDFS plugin, user-store loading, admin audits storage, reduced plugin > >> > memory footprint > >> > HA support for user-sync and tag-sync services > >> > Introduction of Metrics API > >> > Security zone supports admin-roles and auditor-roles > >> > Option to use user-groups associations in Ranger during authorization > in > >> > plugins > >> > Support to grant time-bound accesses at policy-item level > >> > Python client API to manage users, groups, user-group associations > >> > Kafka authorizer updates for KIP-504 > >> > API to purge x_policy_export_audit, x_trx_log tables > >> > Docker setup for Trino configured with Ranger authorizer > >> > Dependent libraries version updates > >> > > >> > > >> > The Apache Ranger PMC would appreciate your contributions and feedback > >> in > >> > getting 2.5.0 release out. > >> > > >> > > >> > > >> > Thanks, > >> > > >> > Madhan > >> > > >> > Apache Ranger PMC Member > >> > > >> > > >> > >> > >> > >> > >> > > > > >
Re: Review Request 74963: RANGER-4780: Ranger - Upgrade json-smart to 2.4.10
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74963/#review226690 --- Can you confirm in the KMS classpath json-smart dependency is updated or not? - bhavik patel On June 17, 2024, 6:26 a.m., Rakesh Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74963/ > --- > > (Updated June 17, 2024, 6:26 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > sanket shelar, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4780 > https://issues.apache.org/jira/browse/RANGER-4780 > > > Repository: ranger > > > Description > --- > > Ranger - Upgrade json-smart to 2.4.10 > > > Diffs > - > > knox-agent/pom.xml 4387efb5c > plugin-schema-registry/pom.xml 4be8cff8d > ranger-authn/pom.xml bd8ab1048 > ranger-knox-plugin-shim/pom.xml e83e4296a > ugsync/pom.xml ed06fd718 > unixauthclient/pom.xml c7fc6f33e > unixauthservice/pom.xml c26738ff6 > > > Diff: https://reviews.apache.org/r/74963/diff/1/ > > > Testing > --- > > mvn clean compile package install > Sanity testing completed with json-smart version 2.4.10 > > > Thanks, > > Rakesh Gupta > >
[jira] [Updated] (RANGER-4859) Update Trino service-def in Ranger for authorization changes
[ https://issues.apache.org/jira/browse/RANGER-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4859: - Fix Version/s: 2.5.0 > Update Trino service-def in Ranger for authorization changes > > > Key: RANGER-4859 > URL: https://issues.apache.org/jira/browse/RANGER-4859 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4859) Update Trino service-def in Ranger for authorization changes
[ https://issues.apache.org/jira/browse/RANGER-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866620#comment-17866620 ] Bhavik Patel commented on RANGER-4859: -- ohh ok. Thanks [~pradeep] for the clarification. > Update Trino service-def in Ranger for authorization changes > > > Key: RANGER-4859 > URL: https://issues.apache.org/jira/browse/RANGER-4859 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4859) Update Trino service-def in Ranger for authorization changes
[ https://issues.apache.org/jira/browse/RANGER-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866614#comment-17866614 ] Bhavik Patel commented on RANGER-4859: -- [~madhan] I think patch is not completed yet. As JAVA patch number 61 is mentioned in the schema file but actual class file is not present in the patch. > Update Trino service-def in Ranger for authorization changes > > > Key: RANGER-4859 > URL: https://issues.apache.org/jira/browse/RANGER-4859 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Apache Ranger 2.5.0 release
Hello Rangers, Gn that we have two open major issues https://issues.apache.org/jira/browse/RANGER-4804 and https://issues.apache.org/jira/browse/RANGER-4851, we plan to distribute the first release candidate for voting this thursday or friday. Regard, Bhavik Patel +91-7208744109 On Wed, Jul 10, 2024 at 3:47 PM Bhavik Patel wrote: > Thanks Madhan. > > @Ranger community, > > Please review the following brief plan and let me know if you have any > comments: > > > 1. 2024-07-31, Wed: tentative release date > > 2. 2022-07-12, Fri: release branch will be closed for commits. After this > date, commits will require approval from the PMCs > > 3. 2022-07-16, Tue: first release candidate out for vote > > 4. 2022-07-25, Thu: tentative vote completion. > > > Looking forward to your help in making the 2.5.0 release as planned. > > > Regard, > Bhavik Patel > +91-7208744109 > > > On Wed, Jul 10, 2024 at 2:12 PM Madhan Neethiraj > wrote: > >> Bhavik, >> >> Thank you for volunteering to be the release manager. As suggested >> earlier, let's target 2.5.0 release by end of this month. >> >> Thanks, >> Madhan >> >> >> >> >> On 7/9/24, 12:28 AM, "Bhavik Patel" > bhavikpatel...@gmail.com>> wrote: >> >> >> Thank you, Madhan, for getting the ball rolling on the release of newer >> version for Ranger. >> >> >> I would like to lead the release activity for the Apache Ranger version >> 2.5.0 and have created jira RANGER-4844 to monitor and follow up the >> release activities. >> >> >> >> >> Thanks, >> Bhavik Patel >> +91-7208744109 >> >> >> >> >> >> >> On Fri, 28 Jun 2024, 6:11 am Madhan Neethiraj, > <mailto:mad...@apache.org>> wrote: >> >> >> > Ranger community, >> > >> > >> > >> > It has been 15 months since the last release of Apache Ranger, 2.4.0. >> > During this time, the community has added 500 commits with several >> > improvements, fixes, and new features. I propose we start preparing for >> the >> > release of Apache Ranger 2.5.0 to include all these enhancements by end >> of >> > July 2024. >> > >> > >> > >> > The branch ranger-2.5.0 will be used for this release. If you would like >> > any improvement or fix to be included in this release, please ensure the >> > fix-version is set to 2.5.0 in JIRA. >> > >> > >> > >> > Here are few key improvements: >> > New UI implemented using React, replacing Backbone UI >> > Performance improvements in several modules >> > HDFS plugin, user-store loading, admin audits storage, reduced plugin >> > memory footprint >> > HA support for user-sync and tag-sync services >> > Introduction of Metrics API >> > Security zone supports admin-roles and auditor-roles >> > Option to use user-groups associations in Ranger during authorization in >> > plugins >> > Support to grant time-bound accesses at policy-item level >> > Python client API to manage users, groups, user-group associations >> > Kafka authorizer updates for KIP-504 >> > API to purge x_policy_export_audit, x_trx_log tables >> > Docker setup for Trino configured with Ranger authorizer >> > Dependent libraries version updates >> > >> > >> > The Apache Ranger PMC would appreciate your contributions and feedback >> in >> > getting 2.5.0 release out. >> > >> > >> > >> > Thanks, >> > >> > Madhan >> > >> > Apache Ranger PMC Member >> > >> > >> >> >> >> >>
Re: Apache Ranger 2.5.0 release
Thanks Madhan. @Ranger community, Please review the following brief plan and let me know if you have any comments: 1. 2024-07-31, Wed: tentative release date 2. 2022-07-12, Fri: release branch will be closed for commits. After this date, commits will require approval from the PMCs 3. 2022-07-16, Tue: first release candidate out for vote 4. 2022-07-25, Thu: tentative vote completion. Looking forward to your help in making the 2.5.0 release as planned. Regard, Bhavik Patel +91-7208744109 On Wed, Jul 10, 2024 at 2:12 PM Madhan Neethiraj wrote: > Bhavik, > > Thank you for volunteering to be the release manager. As suggested > earlier, let's target 2.5.0 release by end of this month. > > Thanks, > Madhan > > > > > On 7/9/24, 12:28 AM, "Bhavik Patel" bhavikpatel...@gmail.com>> wrote: > > > Thank you, Madhan, for getting the ball rolling on the release of newer > version for Ranger. > > > I would like to lead the release activity for the Apache Ranger version > 2.5.0 and have created jira RANGER-4844 to monitor and follow up the > release activities. > > > > > Thanks, > Bhavik Patel > +91-7208744109 > > > > > > > On Fri, 28 Jun 2024, 6:11 am Madhan Neethiraj, mad...@apache.org>> wrote: > > > > Ranger community, > > > > > > > > It has been 15 months since the last release of Apache Ranger, 2.4.0. > > During this time, the community has added 500 commits with several > > improvements, fixes, and new features. I propose we start preparing for > the > > release of Apache Ranger 2.5.0 to include all these enhancements by end > of > > July 2024. > > > > > > > > The branch ranger-2.5.0 will be used for this release. If you would like > > any improvement or fix to be included in this release, please ensure the > > fix-version is set to 2.5.0 in JIRA. > > > > > > > > Here are few key improvements: > > New UI implemented using React, replacing Backbone UI > > Performance improvements in several modules > > HDFS plugin, user-store loading, admin audits storage, reduced plugin > > memory footprint > > HA support for user-sync and tag-sync services > > Introduction of Metrics API > > Security zone supports admin-roles and auditor-roles > > Option to use user-groups associations in Ranger during authorization in > > plugins > > Support to grant time-bound accesses at policy-item level > > Python client API to manage users, groups, user-group associations > > Kafka authorizer updates for KIP-504 > > API to purge x_policy_export_audit, x_trx_log tables > > Docker setup for Trino configured with Ranger authorizer > > Dependent libraries version updates > > > > > > The Apache Ranger PMC would appreciate your contributions and feedback in > > getting 2.5.0 release out. > > > > > > > > Thanks, > > > > Madhan > > > > Apache Ranger PMC Member > > > > > > > > >
Re: Review Request 75078: RANGER-4845: removed guava dependency
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75078/#review226642 --- Ship it! Ship It! - bhavik patel On July 9, 2024, 7:46 a.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/75078/ > --- > > (Updated July 9, 2024, 7:46 a.m.) > > > Review request for ranger, Abhishek Kumar, Bhavik Bavishi, Fateh Singh, > Kishor Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Mugdha Varadkar, Pradeep > Agrawal, Ramesh Mani, Sailaja Polavarapu, Velmurugan Periasamy, and zhongwei > wang. > > > Bugs: RANGER-4845 > https://issues.apache.org/jira/browse/RANGER-4845 > > > Repository: ranger > > > Description > --- > > - replaced use of following guava classes/pacakges: > -- com.google.common.base.Strings => org.apache.commons.lang3.StringUtils > -- com.google.common.base => > org.apache.hadoop.thirdparty.com.google.common.base > -- com.google.common.collect => > org.apache.hadoop.thirdparty.com.google.common.collect > -- com.google.common.annotations => > org.apache.hadoop.thirdparty.com.google.common.annotations > -- com.google.common.util.concurrent.ThreadFactoryBuilder => > org.apache.hadoop.thirdparty.com.google.common.util.concurrent.ThreadFactoryBuilder > - updated pom files to remove dependency on guava library > - updated distro to remove packaging of guava library > > > Diffs > - > > agents-audit/pom.xml 06e81650f > > agents-audit/src/main/java/org/apache/ranger/audit/destination/ElasticSearchAuditDestination.java > b81c30e51 > > agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerServiceDefHelper.java > 51a3aae6f > > agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerServiceDefValidator.java > 9cbea7f61 > > agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerServiceValidator.java > 5521146b9 > > agents-common/src/main/java/org/apache/ranger/plugin/util/PasswordUtils.java > f1f2b0920 > > agents-common/src/main/java/org/apache/ranger/plugin/util/PerfDataRecorder.java > a1df53fac > > agents-common/src/test/java/org/apache/ranger/plugin/conditionevaluator/RangerTimeOfDayMatcherTest.java > ec64e33e4 > > agents-common/src/test/java/org/apache/ranger/plugin/errors/TestValidationErrorCode.java > 2c69bcc6f > > agents-common/src/test/java/org/apache/ranger/plugin/model/validation/TestDirectedGraph.java > 3ec20d99a > > agents-common/src/test/java/org/apache/ranger/plugin/model/validation/TestRangerPolicyValidator.java > 7e16082bc > > agents-common/src/test/java/org/apache/ranger/plugin/model/validation/TestRangerServiceDefHelper.java > b0c108530 > > agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerDefaultResourceMatcherTest.java > 8a297bde0 > > agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerPathResourceMatcherTest.java > 3727b30d4 > > agents-common/src/test/java/org/apache/ranger/plugin/resourcematcher/RangerURLResourceMatcherTest.java > cc7307615 > > agents-common/src/test/java/org/apache/ranger/plugin/util/PasswordUtilsTest.java > d0b180645 > credentialbuilder/pom.xml 0f61148ee > distro/src/main/assembly/admin-web.xml 0c8afa9d0 > distro/src/main/assembly/hbase-agent.xml b36652091 > distro/src/main/assembly/hdfs-agent.xml 498b2ff2b > distro/src/main/assembly/hive-agent.xml 17757f90b > distro/src/main/assembly/kms.xml c9b863088 > distro/src/main/assembly/knox-agent.xml e97a9c6c8 > distro/src/main/assembly/plugin-atlas.xml ed0108475 > distro/src/main/assembly/plugin-elasticsearch.xml a627f641b > distro/src/main/assembly/plugin-kafka.xml 782f0ab79 > distro/src/main/assembly/plugin-kms.xml 928db2041 > distro/src/main/assembly/plugin-kylin.xml 968197a4a > distro/src/main/assembly/plugin-ozone.xml f1b78699c > distro/src/main/assembly/plugin-presto.xml b5fced211 > distro/src/main/assembly/plugin-solr.xml fb05fa2af > distro/src/main/assembly/plugin-sqoop.xml 37c1a6f8f > distro/src/main/assembly/plugin-trino.xml a2f4828a4 > distro/src/main/assembly/plugin-yarn.xml 9f112dcbf > distro/src/main/assembly/ranger-tools.xml 518615c9b > distro/src/main/assembly/sample-client.xml b7c73ef8b > distro/src/main/assembly/storm-
Re: Apache Ranger 2.5.0 release
Thank you, Madhan, for getting the ball rolling on the release of newer version for Ranger. I would like to lead the release activity for the Apache Ranger version 2.5.0 and have created jira RANGER-4844 to monitor and follow up the release activities. Thanks, Bhavik Patel +91-7208744109 On Fri, 28 Jun 2024, 6:11 am Madhan Neethiraj, wrote: > Ranger community, > > > > It has been 15 months since the last release of Apache Ranger, 2.4.0. > During this time, the community has added 500 commits with several > improvements, fixes, and new features. I propose we start preparing for the > release of Apache Ranger 2.5.0 to include all these enhancements by end of > July 2024. > > > > The branch ranger-2.5.0 will be used for this release. If you would like > any improvement or fix to be included in this release, please ensure the > fix-version is set to 2.5.0 in JIRA. > > > > Here are few key improvements: > New UI implemented using React, replacing Backbone UI > Performance improvements in several modules > HDFS plugin, user-store loading, admin audits storage, reduced plugin > memory footprint > HA support for user-sync and tag-sync services > Introduction of Metrics API > Security zone supports admin-roles and auditor-roles > Option to use user-groups associations in Ranger during authorization in > plugins > Support to grant time-bound accesses at policy-item level > Python client API to manage users, groups, user-group associations > Kafka authorizer updates for KIP-504 > API to purge x_policy_export_audit, x_trx_log tables > Docker setup for Trino configured with Ranger authorizer > Dependent libraries version updates > > > The Apache Ranger PMC would appreciate your contributions and feedback in > getting 2.5.0 release out. > > > > Thanks, > > Madhan > > Apache Ranger PMC Member > >
[jira] [Created] (RANGER-4847) Publish release artifacts
Bhavik Patel created RANGER-4847: Summary: Publish release artifacts Key: RANGER-4847 URL: https://issues.apache.org/jira/browse/RANGER-4847 Project: Ranger Issue Type: Sub-task Components: Ranger Affects Versions: 2.4.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Fix For: 2.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4846) Update Apache Ranger website with 2.5.0
Bhavik Patel created RANGER-4846: Summary: Update Apache Ranger website with 2.5.0 Key: RANGER-4846 URL: https://issues.apache.org/jira/browse/RANGER-4846 Project: Ranger Issue Type: Sub-task Components: Ranger Affects Versions: 2.4.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Fix For: 2.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4825) update ranger-2.5 branch pom.xml version to 2.5.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/RANGER-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4825: - Parent: RANGER-4844 Issue Type: Sub-task (was: Task) > update ranger-2.5 branch pom.xml version to 2.5.0-SNAPSHOT > -- > > Key: RANGER-4825 > URL: https://issues.apache.org/jira/browse/RANGER-4825 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.5.0 > > Attachments: RANGER-4825.patch > > > To get started with Apache Ranger 2.5 release, create branch ranger-2.5 and > update pom.xml to set version to 2.5.0-SNAPSHOT -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4844) Release Apache Ranger 2.5.0
Bhavik Patel created RANGER-4844: Summary: Release Apache Ranger 2.5.0 Key: RANGER-4844 URL: https://issues.apache.org/jira/browse/RANGER-4844 Project: Ranger Issue Type: Task Components: Ranger Affects Versions: 2.4.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Fix For: 2.5.0 Tracking 2.5.0 release tasks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4816) build Trino Ranger plugin in Trino project
[ https://issues.apache.org/jira/browse/RANGER-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860124#comment-17860124 ] Bhavik Patel commented on RANGER-4816: -- Hi [~madhan] Is the PR raised for the trino repo? > build Trino Ranger plugin in Trino project > -- > > Key: RANGER-4816 > URL: https://issues.apache.org/jira/browse/RANGER-4816 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Attachments: RANGER-4816-trio-repo.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74955: RANGER-4729: Upgrade commons-compress to 1.26.0
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74955/#review226482 --- Ship it! Ship It! - bhavik patel On April 10, 2024, 9:31 a.m., Rakesh Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74955/ > --- > > (Updated April 10, 2024, 9:31 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Mehul > Parikh, Pradeep Agrawal, and sanket shelar. > > > Bugs: RANGER-4729 > https://issues.apache.org/jira/browse/RANGER-4729 > > > Repository: ranger > > > Description > --- > > Upgrade commons-compress to 1.26.0 > > > Diffs > - > > pom.xml efd152040 > > > Diff: https://reviews.apache.org/r/74955/diff/1/ > > > Testing > --- > > Sanity testing completed with commons-compress version 1.26.0 > > > Thanks, > > Rakesh Gupta > >
Review Request 75008: RANGER-4800:Ranger Tagsync service start failed when ranger admin is SSL enabled
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/75008/ --- Review request for ranger. Bugs: RANGER-4800 https://issues.apache.org/jira/browse/RANGER-4800 Repository: ranger Description --- Ranger Tagsync service start failed when ranger admin is SSL enabled with below error: ERROR o.a.r.t.p.TagSynchronizer [main] - 230 Failed to initialize TAG sink. Error details: java.lang.NoClassDefFoundError: org/apache/ranger/authorization/hadoop/utils/RangerCredentialProvider at org.apache.ranger.plugin.util.RangerRESTClient.getCredential(RangerRESTClient.java:433) at org.apache.ranger.plugin.util.RangerRESTClient.getKeyManagers(RangerRESTClient.java:291) at org.apache.ranger.plugin.util.RangerRESTClient.buildClient(RangerRESTClient.java:205) at org.apache.ranger.plugin.util.RangerRESTClient.getClient(RangerRESTClient.java:193) at org.apache.ranger.tagsync.sink.tagadmin.TagAdminRESTSink.initialize(TagAdminRESTSink.java:106) at org.apache.ranger.tagsync.process.TagSynchronizer.initializeTagSink(TagSynchronizer.java:225) at org.apache.ranger.tagsync.process.TagSynchronizer.initialize(TagSynchronizer.java:110) at org.apache.ranger.tagsync.process.TagSynchronizer.main(TagSynchronizer.java:65) Caused by: java.lang.ClassNotFoundException: org.apache.ranger.authorization.hadoop.utils.RangerCredentialProvider at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) ... 8 common frames omitted Diffs - tagsync/pom.xml a1445fdd8 Diff: https://reviews.apache.org/r/75008/diff/1/ Testing --- after adding the dependency, tagsync service started without any error and tags are synced to ranger admin. Thanks, bhavik patel
[jira] [Updated] (RANGER-4800) Ranger Tagsync service start failed when ranger admin is SSL enabled
[
https://issues.apache.org/jira/browse/RANGER-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhavik Patel updated RANGER-4800:
-
Attachment: 0001-RANGER-4800-Ranger-Tagsync-service-start-failed-when.patch
> Ranger Tagsync service start failed when ranger admin is SSL enabled
>
>
> Key: RANGER-4800
> URL: https://issues.apache.org/jira/browse/RANGER-4800
> Project: Ranger
> Issue Type: Bug
> Components: tagsync
>Affects Versions: 2.4.0
>Reporter: Bhavik Patel
> Assignee: Bhavik Patel
>Priority: Major
> Attachments:
> 0001-RANGER-4800-Ranger-Tagsync-service-start-failed-when.patch
>
>
> Ranger Tagsync service start failed when ranger admin is SSL enabled with
> below error:
> {code:java}
> ERROR o.a.r.t.p.TagSynchronizer [main] - 230 Failed to initialize TAG sink.
> Error details:
> java.lang.NoClassDefFoundError:
> org/apache/ranger/authorization/hadoop/utils/RangerCredentialProvider
> at
> org.apache.ranger.plugin.util.RangerRESTClient.getCredential(RangerRESTClient.java:433)
> at
> org.apache.ranger.plugin.util.RangerRESTClient.getKeyManagers(RangerRESTClient.java:291)
> at
> org.apache.ranger.plugin.util.RangerRESTClient.buildClient(RangerRESTClient.java:205)
> at
> org.apache.ranger.plugin.util.RangerRESTClient.getClient(RangerRESTClient.java:193)
> at
> org.apache.ranger.tagsync.sink.tagadmin.TagAdminRESTSink.initialize(TagAdminRESTSink.java:106)
> at
> org.apache.ranger.tagsync.process.TagSynchronizer.initializeTagSink(TagSynchronizer.java:225)
> at
> org.apache.ranger.tagsync.process.TagSynchronizer.initialize(TagSynchronizer.java:110)
> at
> org.apache.ranger.tagsync.process.TagSynchronizer.main(TagSynchronizer.java:65)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ranger.authorization.hadoop.utils.RangerCredentialProvider
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
> ... 8 common frames omitted
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4800) Ranger Tagsync service start failed when ranger admin is SSL enabled
Bhavik Patel created RANGER-4800:
Summary: Ranger Tagsync service start failed when ranger admin is
SSL enabled
Key: RANGER-4800
URL: https://issues.apache.org/jira/browse/RANGER-4800
Project: Ranger
Issue Type: Bug
Components: tagsync
Affects Versions: 2.4.0
Reporter: Bhavik Patel
Assignee: Bhavik Patel
Ranger Tagsync service start failed when ranger admin is SSL enabled with below
error:
{code:java}
ERROR o.a.r.t.p.TagSynchronizer [main] - 230 Failed to initialize TAG sink.
Error details:
java.lang.NoClassDefFoundError:
org/apache/ranger/authorization/hadoop/utils/RangerCredentialProvider
at
org.apache.ranger.plugin.util.RangerRESTClient.getCredential(RangerRESTClient.java:433)
at
org.apache.ranger.plugin.util.RangerRESTClient.getKeyManagers(RangerRESTClient.java:291)
at
org.apache.ranger.plugin.util.RangerRESTClient.buildClient(RangerRESTClient.java:205)
at
org.apache.ranger.plugin.util.RangerRESTClient.getClient(RangerRESTClient.java:193)
at
org.apache.ranger.tagsync.sink.tagadmin.TagAdminRESTSink.initialize(TagAdminRESTSink.java:106)
at
org.apache.ranger.tagsync.process.TagSynchronizer.initializeTagSink(TagSynchronizer.java:225)
at
org.apache.ranger.tagsync.process.TagSynchronizer.initialize(TagSynchronizer.java:110)
at
org.apache.ranger.tagsync.process.TagSynchronizer.main(TagSynchronizer.java:65)
Caused by: java.lang.ClassNotFoundException:
org.apache.ranger.authorization.hadoop.utils.RangerCredentialProvider
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
... 8 common frames omitted
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848127#comment-17848127 ] Bhavik Patel commented on RANGER-3409: -- [~sercan.tekin] I have reviewed your PR but i can see still the usage of "codehaus" package. > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Attachments: ranger-modify-policy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846617#comment-17846617 ] Bhavik Patel commented on RANGER-3409: -- Correct [~sercan.tekin]. Just curious to know how it is working for [~n.blagodarny] . > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3409) Update Jackson and remove Codehaus version
[ https://issues.apache.org/jira/browse/RANGER-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846588#comment-17846588 ] Bhavik Patel commented on RANGER-3409: -- Thanks [~n.blagodarny] . While validating your changes I observed users are not visible in the ranger admin web ui. After debugging found that while migrating from Codehaus Jackson to FasterXML Jackson property naming strategy was changed to lowercase and on the frontend we are expecting the original object(without any conversion). Just wondering how does this worked for you. > Update Jackson and remove Codehaus version > -- > > Key: RANGER-3409 > URL: https://issues.apache.org/jira/browse/RANGER-3409 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Andrew Charneski >Priority: Blocker > Time Spent: 0.5h > Remaining Estimate: 0h > > An old version of Jackson (Codehaus Jackson 1.9.13) is still being used. > Jackson has since moved namespaces with a reorganized library structure. > Update all references to the older version to use the newer version (which is > currently used in some modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74926: RANGER-4076: Support Java 17 for build and runtime
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74926/#review226427 --- pom.xml Line 122 (original), 122 (patched) <https://reviews.apache.org/r/74926/#comment314631> any specific reason to downgrade the graalvm version? pom.xml Lines 374 (patched) <https://reviews.apache.org/r/74926/#comment314632> enunciate version depends on jdk? - bhavik patel On May 9, 2024, 3:03 p.m., Rakesh Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74926/ > --- > > (Updated May 9, 2024, 3:03 p.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > sanket shelar, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4076 > https://issues.apache.org/jira/browse/RANGER-4076 > > > Repository: ranger > > > Description > --- > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. > > This patch enables manual and Docker-based build of Apache Ranger. It ensures > compatibility with Java 8, Java 11, and Java 17 for both build and runtime > environments. > > > Diffs > - > > agents-common/pom.xml 12e093f78 > > agents-common/src/main/java/org/apache/ranger/plugin/conditionevaluator/RangerScriptConditionEvaluator.java > 6eb192270 > > agents-common/src/main/java/org/apache/ranger/plugin/util/GraalScriptEngineCreator.java > 512d8d3ca > > agents-common/src/main/java/org/apache/ranger/plugin/util/JavaScriptEngineCreator.java > 4a0081579 > > agents-common/src/main/java/org/apache/ranger/plugin/util/NashornScriptEngineCreator.java > db620df92 > > agents-common/src/main/java/org/apache/ranger/plugin/util/ScriptEngineUtil.java > 8d76c1d81 > > agents-common/src/test/java/org/apache/ranger/plugin/conditionevaluator/RangerRequestScriptEvaluatorTest.java > 0059bef88 > dev-support/ranger-docker/.env 91613e5ec > dev-support/ranger-docker/Dockerfile.ranger-base 72a850482 > dev-support/ranger-docker/Dockerfile.ranger-build 9a192f152 > dev-support/ranger-docker/docker-compose.ranger-build.yml c8760aab5 > dev-support/ranger-docker/scripts/ranger-hadoop-setup.sh 10f04acd9 > dev-support/ranger-docker/scripts/ranger-hbase-setup.sh 95a1bdf21 > distro/src/main/assembly/admin-web.xml 245d9ca09 > distro/src/main/assembly/hbase-agent.xml ffb1de0c5 > distro/src/main/assembly/hdfs-agent.xml 349badfd2 > distro/src/main/assembly/hive-agent.xml 5bae92ac5 > distro/src/main/assembly/knox-agent.xml 3fa867150 > distro/src/main/assembly/plugin-atlas.xml c389282fc > distro/src/main/assembly/plugin-kafka.xml 4ffbdd611 > distro/src/main/assembly/plugin-kms.xml 7c6a16330 > distro/src/main/assembly/plugin-kylin.xml 9aefa49d4 > distro/src/main/assembly/plugin-ozone.xml 294e5b9ef > distro/src/main/assembly/plugin-presto.xml d50edf2d9 > distro/src/main/assembly/plugin-solr.xml bcb24c0fc > distro/src/main/assembly/plugin-sqoop.xml adc2a9c26 > distro/src/main/assembly/plugin-yarn.xml 5db884710 > distro/src/main/assembly/storm-agent.xml a334e247c > docs/src/site/resources/index.js bb876f28d > hdfs-agent/pom.xml dece8f46f > kms/pom.xml bfac6424a > kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java > b6fc32950 > knox-agent/pom.xml 4387efb5c > plugin-nestedstructure/pom.xml 0e208f99c > > plugin-nestedstructure/src/main/java/org/apache/ranger/authorization/nestedstructure/authorizer/RecordFilterJavaScript.java > 77767767c > > plugin-nestedstructure/src/test/java/org/apache/ranger/authorization/nestedstructure/authorizer/TestRecordFilterJavaScript.java > 9cb161b8d > pom.xml efd152040 > security-admin/pom.xml fc59287d0 > > > Diff: https://reviews.apache.org/r/74926/diff/4/ > > > Testing > --- > > This patch has been successfully tested and verified with Java versions 8, > 11, and 17. The verification process included both manual and Docker setup. > Now we are able to build and run on same jdk. > > ### JDK 8 maven build successfully > mvn clean compile package install > > ### JDK 11 maven build successfully > mvn clean compile package install > > ### JDK 17 maven build successfully > mvn clean compile pack
[jira] [Commented] (RANGER-4225) Possible Jackson serialization issue due to not comply with Java bean standards
[
https://issues.apache.org/jira/browse/RANGER-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843650#comment-17843650
]
Bhavik Patel commented on RANGER-4225:
--
[~sercan.tekin] are you working on this?
> Possible Jackson serialization issue due to not comply with Java bean
> standards
> ---
>
> Key: RANGER-4225
> URL: https://issues.apache.org/jira/browse/RANGER-4225
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
>Reporter: Sercan Tekin
>Assignee: Sercan Tekin
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4225.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> +*PROBLEM:*+
> Transitive Jackson-2 dependencies are included into Ranger's classpath in my
> env and conflicted with Jackson-1 dependencies.
> Jackson-2 uses Javabean naming conventions to figure out the Json properties
> in a Java class, and some of the Ranger's model classes don't comply with the
> convention.
> For example, when the leading camelcase word is only one letter in length,
> then deserialized response is broken. The following is what I observed in
> Ranger v2.4.0;
> On Ranger UI side, this
> [code-block|https://github.com/apache/ranger/blob/ranger-1.2/security-admin/src/main/webapp/scripts/views/policies/PermissionList.js#L224-L229]
> attempts to read vXStrings key in map, but the corresponding response has
> vxstrings instead:
> {code:java}
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 11,
> "resultSize": 11,
> "sortType": "asc",
> "sortBy": "id",
> "listSize": 11,
> "vxstrings": [< here! This has to be vXStrings
> {
> "value": "public",
> ... {code}
> And this difference causes below error while reading the property, therefore
> the corresponding dropdown has no values as excepted;
> {code:java}
> PermissionList.js?ver=build.version:226 Uncaught TypeError: Cannot read
> properties of undefined (reading 'map')
> at Object.results (PermissionList.js?ver=build.version:226:34)
> at Object.success (select2.js?ver=build.version:450:47)
> at u (jquery-3.3.1.min.js?ver=build.version:2:27457)
> at Object.fireWith [as resolveWith]
> (jquery-3.3.1.min.js?ver=build.version:2:28202)
> at k (jquery-3.3.1.min.js?ver=build.version:2:77651)
> at XMLHttpRequest.
> (jquery-3.3.1.min.js?ver=build.version:2:79907){code}
> +*REFERENCES:*+
> Please see this reference related to capital letters
> [http://futuretask.blogspot.com/2005/01/java-tip-6-dont-capitalize-first-two.html]
> "Don't capitalize first two letters of a bean property name. This is in our
> java standards. You should not create a java bean property name that begins
> with a capital letter in the 1st two places."
> Also you can see the same issue is reported here
> [https://stackoverflow.com/questions/30205006/why-does-jackson-2-not-recognize-the-first-capital-letter-if-the-leading-camel-c]
>
> +*SOLUTION:*+
> {{@JsonProperty}} annotation needs to be added for mapping the properties
> with their corresponding getter/setter methods. This will not effect Ranger's
> functionality directly, but it will provide consistency even if Jackson-2 is
> included into classpath.
> I have tested it locally after adding {{@JsonProperty}} and everything worked
> well.
> The PR is attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74926: RANGER-4076: Support Java 17 for build and runtime
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74926/#review226395 --- Have you validated the policy enforcement for any plugin? - bhavik patel On April 23, 2024, 12:32 p.m., Rakesh Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74926/ > --- > > (Updated April 23, 2024, 12:32 p.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > sanket shelar, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4076 > https://issues.apache.org/jira/browse/RANGER-4076 > > > Repository: ranger > > > Description > --- > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. > > This patch enables manual and Docker-based build of Apache Ranger. It ensures > compatibility with Java 8, Java 11, and Java 17 for both build and runtime > environments. > > > Diffs > - > > agents-common/pom.xml 12e093f78 > > agents-common/src/main/java/org/apache/ranger/plugin/conditionevaluator/RangerScriptConditionEvaluator.java > 6eb192270 > > agents-common/src/main/java/org/apache/ranger/plugin/util/GraalScriptEngineCreator.java > 512d8d3ca > > agents-common/src/main/java/org/apache/ranger/plugin/util/JavaScriptEngineCreator.java > 4a0081579 > > agents-common/src/main/java/org/apache/ranger/plugin/util/NashornScriptEngineCreator.java > db620df92 > > agents-common/src/main/java/org/apache/ranger/plugin/util/ScriptEngineUtil.java > 8d76c1d81 > > agents-common/src/test/java/org/apache/ranger/plugin/conditionevaluator/RangerRequestScriptEvaluatorTest.java > 0059bef88 > dev-support/ranger-docker/.env 91613e5ec > dev-support/ranger-docker/Dockerfile.ranger-build 9a192f152 > dev-support/ranger-docker/docker-compose.ranger-build.yml c8760aab5 > distro/src/main/assembly/admin-web.xml 245d9ca09 > distro/src/main/assembly/hbase-agent.xml ffb1de0c5 > distro/src/main/assembly/hdfs-agent.xml 349badfd2 > distro/src/main/assembly/hive-agent.xml 5bae92ac5 > distro/src/main/assembly/knox-agent.xml 3fa867150 > distro/src/main/assembly/plugin-atlas.xml c389282fc > distro/src/main/assembly/plugin-kafka.xml 4ffbdd611 > distro/src/main/assembly/plugin-kms.xml 7c6a16330 > distro/src/main/assembly/plugin-kylin.xml 9aefa49d4 > distro/src/main/assembly/plugin-ozone.xml 294e5b9ef > distro/src/main/assembly/plugin-presto.xml d50edf2d9 > distro/src/main/assembly/plugin-solr.xml bcb24c0fc > distro/src/main/assembly/plugin-sqoop.xml adc2a9c26 > distro/src/main/assembly/plugin-yarn.xml 5db884710 > distro/src/main/assembly/storm-agent.xml a334e247c > docs/src/site/resources/index.js bb876f28d > hdfs-agent/pom.xml dece8f46f > kms/pom.xml 0b37ce52d > kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java > b6fc32950 > knox-agent/pom.xml 4387efb5c > plugin-nestedstructure/pom.xml 0e208f99c > > plugin-nestedstructure/src/main/java/org/apache/ranger/authorization/nestedstructure/authorizer/RecordFilterJavaScript.java > 77767767c > > plugin-nestedstructure/src/test/java/org/apache/ranger/authorization/nestedstructure/authorizer/TestRecordFilterJavaScript.java > 9cb161b8d > pom.xml efd152040 > security-admin/pom.xml fc59287d0 > > > Diff: https://reviews.apache.org/r/74926/diff/3/ > > > Testing > --- > > This patch has been successfully tested and verified with Java versions 8, > 11, and 17. The verification process included both manual and Docker setup. > Now we are able to build and run on same jdk. > > ### JDK 8 maven build successfully > mvn clean compile package install > > ### JDK 11 maven build successfully > mvn clean compile package install > > ### JDK 17 maven build successfully > mvn clean compile package install -Pranger-all-modules-jdk17 > > > Thanks, > > Rakesh Gupta > >
[jira] [Commented] (RANGER-4622) Fix the default value of ranger.accesslog.rotate.rename_on_rotate configuration in ranger--admin-default-site.xml
[ https://issues.apache.org/jira/browse/RANGER-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832752#comment-17832752 ] Bhavik Patel commented on RANGER-4622: -- +LGTM > Fix the default value of ranger.accesslog.rotate.rename_on_rotate > configuration in ranger--admin-default-site.xml > - > > Key: RANGER-4622 > URL: https://issues.apache.org/jira/browse/RANGER-4622 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 2.3.0 >Reporter: zhaoshuaihua >Priority: Minor > Attachments: > RANGER-4622_property_ranger_accesslog_rotate_rename_on_rotate,_the_default_value_is_false,.patch, > screenshot-1.png > > Original Estimate: 0.5h > Time Spent: 20m > Remaining Estimate: 10m > > Fix the default value of ranger.accesslog.rotate.rename_on_rotate > configuration in ranger--admin-default-site.xml. The default value of this > configuration is false instead of 15. > > !https://private-user-images.githubusercontent.com/50791733/291463576-4dbadd0b-0c89-411f-84bf-9f173dcdfd4c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDMxNDczMzIsIm5iZiI6MTcwMzE0NzAzMiwicGF0aCI6Ii81MDc5MTczMy8yOTE0NjM1NzYtNGRiYWRkMGItMGM4OS00MTFmLTg0YmYtOWYxNzNkY2RmZDRjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjIxVDA4MjM1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThiYTkwZGJhYmM5NWM5YWVlYzhkMTgyYmIyMjhhYzkwMzg3MTUwZmU3YzQ5MTcxMzY1OGQyZWRiMzhiNDEyYzImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.KjaxtRsqR1N9JuBgx4n3_45_tzIa9liHl787PCtqUFo! > !https://private-user-images.githubusercontent.com/50791733/291463606-a72f6e18-fcee-4f8d-8155-fa7cb9eb76e4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDMxNDczMzIsIm5iZiI6MTcwMzE0NzAzMiwicGF0aCI6Ii81MDc5MTczMy8yOTE0NjM2MDYtYTcyZjZlMTgtZmNlZS00ZjhkLTgxNTUtZmE3Y2I5ZWI3NmU0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjIxVDA4MjM1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc3YTg5YjhjZmIxNzUwYjkyYzE1MzBhZjNmOGEwZjI4NGZmODEzMDg5NDQ2M2VkNTU5YmVkNGEyNWEwNDc1M2QmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.k5_0FMEOriQX_Q0_hd7vx5LmOR6p3PV8ozwKQ1p9hv0! -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74944: RANGER-4753: Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74944/#review226359 --- Ship it! Ship It! - bhavik patel On March 22, 2024, 5:25 a.m., Pradeep Agrawal wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74944/ > --- > > (Updated March 22, 2024, 5:25 a.m.) > > > Review request for ranger, Abhishek Patil, Abhishek Kumar, bhavik patel, > Dhaval Shah, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay Kulkarni, Madhan > Neethiraj, Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan > Periasamy. > > > Bugs: RANGER-4753 > https://issues.apache.org/jira/browse/RANGER-4753 > > > Repository: ranger > > > Description > --- > > Here I am proposing to Upgrade Spring Security version to 5.7.12 and spring > framework version to 5.3.33 > > > Diffs > - > > pom.xml cec2390f2 > > > Diff: https://reviews.apache.org/r/74944/diff/1/ > > > Testing > --- > > Tested ranger admin installation, password change, CRUD operation on Ranger > service, policy, users and group. > > > Thanks, > > Pradeep Agrawal > >
Re: Review Request 74926: RANGER-4076: Support Java 17 for build and runtime
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74926/#review226358 --- Can you verify the Usersync, Tagsync and Ranger KMS as well? - bhavik patel On March 5, 2024, 7:10 a.m., Rakesh Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74926/ > --- > > (Updated March 5, 2024, 7:10 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > sanket shelar, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4076 > https://issues.apache.org/jira/browse/RANGER-4076 > > > Repository: ranger > > > Description > --- > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. > > This patch enables manual and Docker-based build of Apache Ranger. It ensures > compatibility with Java 8, Java 11, and Java 17 for both build and runtime > environments. > (I encountered a TestCase Failure in the KnoxRangerTest class, so currently I > had excluded that class from jdk17 build) > > > Diffs > - > > agents-common/pom.xml 12e093f78 > > agents-common/src/main/java/org/apache/ranger/plugin/util/GraalScriptEngineCreator.java > 512d8d3ca > > agents-common/src/main/java/org/apache/ranger/plugin/util/NashornScriptEngineCreator.java > db620df92 > > agents-common/src/main/java/org/apache/ranger/plugin/util/ScriptEngineUtil.java > 8d76c1d81 > dev-support/ranger-docker/.env 60bc4a9f2 > dev-support/ranger-docker/Dockerfile.ranger-build 9a192f152 > dev-support/ranger-docker/docker-compose.ranger-build.yml 3dd4a4a06 > distro/src/main/assembly/admin-web.xml 245d9ca09 > docs/src/site/resources/index.js bb876f28d > hdfs-agent/pom.xml dece8f46f > kms/pom.xml 2739bb81a > kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStore.java > 7188b19b2 > kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java > b6fc32950 > plugin-nestedstructure/pom.xml 0e208f99c > > plugin-nestedstructure/src/main/java/org/apache/ranger/authorization/nestedstructure/authorizer/RecordFilterJavaScript.java > 77767767c > > plugin-nestedstructure/src/test/java/org/apache/ranger/authorization/nestedstructure/authorizer/TestRecordFilterJavaScript.java > 9cb161b8d > pom.xml cec2390f2 > ranger-tools/pom.xml cac8d7ba3 > > ranger-tools/src/test/java/org/apache/ranger/policyengine/RangerPolicyEnginePerformanceTest.java > 187d20227 > security-admin/pom.xml fc59287d0 > > > Diff: https://reviews.apache.org/r/74926/diff/1/ > > > Testing > --- > > This patch has been successfully tested and verified with Java versions 8, > 11, and 17. The verification process included both manual and Docker setup. > Now we are able to build and run on same jdk. > > > Thanks, > > Rakesh Gupta > >
Re: Review Request 74926: RANGER-4076: Support Java 17 for build and runtime
> On March 6, 2024, 3:28 p.m., bhavik patel wrote: > > After starting the server have checked the catalina and ranger admin login > > file? > > Rakesh Gupta wrote: > After starting the server, I checked the Catalina error log, which is > being handled by Jira ticket RANGER-4744. However, the Ranger admin log does > not appear, and this will also be handled by Jira ticket RANGER-4743. it's better as a part of current jira only basic functionality should work. - bhavik --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74926/#review226292 --- On March 5, 2024, 7:10 a.m., Rakesh Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74926/ > --- > > (Updated March 5, 2024, 7:10 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > sanket shelar, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4076 > https://issues.apache.org/jira/browse/RANGER-4076 > > > Repository: ranger > > > Description > --- > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. > > This patch enables manual and Docker-based build of Apache Ranger. It ensures > compatibility with Java 8, Java 11, and Java 17 for both build and runtime > environments. > (I encountered a TestCase Failure in the KnoxRangerTest class, so currently I > had excluded that class from jdk17 build) > > > Diffs > - > > agents-common/pom.xml 12e093f78 > > agents-common/src/main/java/org/apache/ranger/plugin/util/GraalScriptEngineCreator.java > 512d8d3ca > > agents-common/src/main/java/org/apache/ranger/plugin/util/NashornScriptEngineCreator.java > db620df92 > > agents-common/src/main/java/org/apache/ranger/plugin/util/ScriptEngineUtil.java > 8d76c1d81 > dev-support/ranger-docker/.env 60bc4a9f2 > dev-support/ranger-docker/Dockerfile.ranger-build 9a192f152 > dev-support/ranger-docker/docker-compose.ranger-build.yml 3dd4a4a06 > distro/src/main/assembly/admin-web.xml 245d9ca09 > docs/src/site/resources/index.js bb876f28d > hdfs-agent/pom.xml dece8f46f > kms/pom.xml 2739bb81a > kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStore.java > 7188b19b2 > kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java > b6fc32950 > plugin-nestedstructure/pom.xml 0e208f99c > > plugin-nestedstructure/src/main/java/org/apache/ranger/authorization/nestedstructure/authorizer/RecordFilterJavaScript.java > 77767767c > > plugin-nestedstructure/src/test/java/org/apache/ranger/authorization/nestedstructure/authorizer/TestRecordFilterJavaScript.java > 9cb161b8d > pom.xml cec2390f2 > ranger-tools/pom.xml cac8d7ba3 > > ranger-tools/src/test/java/org/apache/ranger/policyengine/RangerPolicyEnginePerformanceTest.java > 187d20227 > security-admin/pom.xml fc59287d0 > > > Diff: https://reviews.apache.org/r/74926/diff/1/ > > > Testing > --- > > This patch has been successfully tested and verified with Java versions 8, > 11, and 17. The verification process included both manual and Docker setup. > Now we are able to build and run on same jdk. > > > Thanks, > > Rakesh Gupta > >
Re: Ranger OS compatability
Yes, it is compatible. On Thu, 21 Mar 2024, 1:54 am Zuniga, Maria, wrote: > Hello Team, > > Is ranger version 2.1 compatible with Rocky ? >
Re: Review Request 74854: RANGER-4672: Tagsync log file name is not containing hostname and user
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74854/#review226293 --- Ship it! Ship It! - bhavik patel On Jan. 24, 2024, 9:52 a.m., Himanshu Maurya wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74854/ > --- > > (Updated Jan. 24, 2024, 9:52 a.m.) > > > Review request for ranger, bhavik patel, Dhaval Shah, Dineshkumar Yadav, > Harshal Chavan, Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Nitin > Galave, Pradeep Agrawal, and Velmurugan Periasamy. > > > Bugs: RANGER-4672 > https://issues.apache.org/jira/browse/RANGER-4672 > > > Repository: ranger > > > Description > --- > > Ranger admin and usersync logs file name is containing hostname and user but > tagsync is missing that > > > Diffs > - > > tagsync/conf.dist/logback.xml c1a94fee4 > tagsync/scripts/ranger-tagsync-services.sh 460c4a130 > > > Diff: https://reviews.apache.org/r/74854/diff/1/ > > > Testing > --- > > Checked the ranger-tagsync log files it is created with correct hostname and > user > > > Thanks, > > Himanshu Maurya > >
Re: Review Request 74926: RANGER-4076: Support Java 17 for build and runtime
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74926/#review226292 --- After starting the server have checked the catalina and ranger admin login file? - bhavik patel On March 5, 2024, 7:10 a.m., Rakesh Gupta wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74926/ > --- > > (Updated March 5, 2024, 7:10 a.m.) > > > Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay > Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, > sanket shelar, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4076 > https://issues.apache.org/jira/browse/RANGER-4076 > > > Repository: ranger > > > Description > --- > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. > > This patch enables manual and Docker-based build of Apache Ranger. It ensures > compatibility with Java 8, Java 11, and Java 17 for both build and runtime > environments. > (I encountered a TestCase Failure in the KnoxRangerTest class, so currently I > had excluded that class from jdk17 build) > > > Diffs > - > > agents-common/pom.xml 12e093f78 > > agents-common/src/main/java/org/apache/ranger/plugin/util/GraalScriptEngineCreator.java > 512d8d3ca > > agents-common/src/main/java/org/apache/ranger/plugin/util/NashornScriptEngineCreator.java > db620df92 > > agents-common/src/main/java/org/apache/ranger/plugin/util/ScriptEngineUtil.java > 8d76c1d81 > dev-support/ranger-docker/.env 60bc4a9f2 > dev-support/ranger-docker/Dockerfile.ranger-build 9a192f152 > dev-support/ranger-docker/docker-compose.ranger-build.yml 3dd4a4a06 > distro/src/main/assembly/admin-web.xml 245d9ca09 > docs/src/site/resources/index.js bb876f28d > hdfs-agent/pom.xml dece8f46f > kms/pom.xml 2739bb81a > kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStore.java > 7188b19b2 > kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java > b6fc32950 > plugin-nestedstructure/pom.xml 0e208f99c > > plugin-nestedstructure/src/main/java/org/apache/ranger/authorization/nestedstructure/authorizer/RecordFilterJavaScript.java > 77767767c > > plugin-nestedstructure/src/test/java/org/apache/ranger/authorization/nestedstructure/authorizer/TestRecordFilterJavaScript.java > 9cb161b8d > pom.xml cec2390f2 > ranger-tools/pom.xml cac8d7ba3 > > ranger-tools/src/test/java/org/apache/ranger/policyengine/RangerPolicyEnginePerformanceTest.java > 187d20227 > security-admin/pom.xml fc59287d0 > > > Diff: https://reviews.apache.org/r/74926/diff/1/ > > > Testing > --- > > This patch has been successfully tested and verified with Java versions 8, > 11, and 17. The verification process included both manual and Docker setup. > Now we are able to build and run on same jdk. > > > Thanks, > > Rakesh Gupta > >
[jira] [Commented] (RANGER-4511) Enable Parallel Compilation for Multiple Modules in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823437#comment-17823437 ] Bhavik Patel commented on RANGER-4511: -- [~jialiang] This would be great if have parallel compilation. [~madhan] Can you also check once. > Enable Parallel Compilation for Multiple Modules in Ranger > -- > > Key: RANGER-4511 > URL: https://issues.apache.org/jira/browse/RANGER-4511 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2023-11-03-11-15-50-593.png, > patch1-RANGER-4511.diff > > Time Spent: 10m > Remaining Estimate: 0h > > "Due to incorrect dependency settings in the distro module, Ranger cannot > utilize multicore concurrent compilation. As a result, compiling Ranger is > very slow each time, as all modules can only be compiled serially. > With this patch, Ranger can be compiled in parallel, greatly speeding up the > process. Compilation can now be completed in just a few minutes. > !image-2023-11-03-11-15-50-593.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4735) Ranger KMS Unable to Start - Missing hadoop-shade-guava JAR
[ https://issues.apache.org/jira/browse/RANGER-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823435#comment-17823435 ] Bhavik Patel commented on RANGER-4735: -- hadoop version upgrade jira: https://issues.apache.org/jira/browse/RANGER-4418 > Ranger KMS Unable to Start - Missing hadoop-shade-guava JAR > --- > > Key: RANGER-4735 > URL: https://issues.apache.org/jira/browse/RANGER-4735 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.4.0 >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2024-03-05-09-34-48-812.png > > > Ranger Kms can't start due to lack hadoop-shade-guava jar > !image-2024-03-05-09-34-48-812.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4735) Ranger KMS Unable to Start - Missing hadoop-shade-guava JAR
[ https://issues.apache.org/jira/browse/RANGER-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823428#comment-17823428 ] Bhavik Patel commented on RANGER-4735: -- Then this is expected, There is already open jira for hadoop version upgrade. > Ranger KMS Unable to Start - Missing hadoop-shade-guava JAR > --- > > Key: RANGER-4735 > URL: https://issues.apache.org/jira/browse/RANGER-4735 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.4.0 >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2024-03-05-09-34-48-812.png > > > Ranger Kms can't start due to lack hadoop-shade-guava jar > !image-2024-03-05-09-34-48-812.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4076) Support Java 17 for build and runtime
[ https://issues.apache.org/jira/browse/RANGER-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823416#comment-17823416 ] Bhavik Patel commented on RANGER-4076: -- [~pradeep] With the current attached patch we are able to build the ranger but we have to also upgrade the hadoop and other component version which supports the JDK-17. With the current patch I'm expecting some issue might observed during/after the ranger KMS upgrade. > Support Java 17 for build and runtime > - > > Key: RANGER-4076 > URL: https://issues.apache.org/jira/browse/RANGER-4076 > Project: Ranger > Issue Type: New Feature > Components: admin, build-infra >Reporter: Andrew Luo >Priority: Major > Attachments: > 0001-RANGER-4076-Support-Java-17-for-build-and-runtime.patch > > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4476) trino filter
[
https://issues.apache.org/jira/browse/RANGER-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823413#comment-17823413
]
Bhavik Patel commented on RANGER-4476:
--
Yes, [~pradeep] We required to do code changes for JDK-17.
There are multiple jira's for trino plugin support and multiple PR's are also
opened. Let's have one common jira and one final PR.
> trino filter
>
>
> Key: RANGER-4476
> URL: https://issues.apache.org/jira/browse/RANGER-4476
> Project: Ranger
> Issue Type: Bug
> Components: plugins, Ranger
>Affects Versions: 3.0.0
>Reporter: Andrey Pilipyuk
>Priority: Major
> Labels: Trino
>
> hello there
> i trying to enable trino plugin, i have successful connect check
> but when i try to make policy i have an error in logs
> 2023-10-16 13:39:09,055 [https-jsse-nio-6182-exec-6] WARN
> [ServiceMgr.java:476] getFilesInDirectory('ranger-plugins/trino'): adding
> /opt/ranger-admin-3.0.0/ews/webapp/WEB-INF/classes/ranger-plugins/trino/trino-jdbc-423.jar
> 2023-10-16 13:39:09,055 [https-jsse-nio-6182-exec-6] WARN
> [ServiceMgr.java:476] getFilesInDirectory('ranger-plugins/trino'): adding
> /opt/ranger-admin-3.0.0/ews/webapp/WEB-INF/classes/ranger-plugins/trino/ranger-trino-plugin-3.0.0-SNAPSHOT.jar
> 2023-10-16 13:39:09,056 [https-jsse-nio-6182-exec-6] WARN
> [ServiceMgr.java:476] getFilesInDirectory('ranger-plugins/trino'): adding
> /opt/ranger-admin-3.0.0/ews/webapp/WEB-INF/classes/ranger-plugins/trino/trino-spi-423.jar
> 2023-10-16 13:39:09,078 [timed-executor-pool-0] WARN
> [SecureClientLogin.java:123] Can't find keyTab Path : null
> 2023-10-16 13:39:09,079 [timed-executor-pool-0] WARN
> [SecureClientLogin.java:127] Can't find principal : null
> 2023-10-16 13:39:09,084 [timed-executor-pool-0] INFO [BaseClient.java:126]
> Init Login: security not enabled, using username
> 2023-10-16 13:39:09,501 [timed-executor-pool-0] ERROR
> [TrinoResourceManager.java:168] Could not initiate a TrinoClient timedTask
> can you please tell me how i can debug it, or some prefirences to trino from
> ranger
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4735) Ranger KMS Unable to Start - Missing hadoop-shade-guava JAR
[ https://issues.apache.org/jira/browse/RANGER-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823412#comment-17823412 ] Bhavik Patel commented on RANGER-4735: -- Which version of hadoop you are using? > Ranger KMS Unable to Start - Missing hadoop-shade-guava JAR > --- > > Key: RANGER-4735 > URL: https://issues.apache.org/jira/browse/RANGER-4735 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.4.0 >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2024-03-05-09-34-48-812.png > > > Ranger Kms can't start due to lack hadoop-shade-guava jar > !image-2024-03-05-09-34-48-812.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4076) Support Java 17 for build and runtime
[ https://issues.apache.org/jira/browse/RANGER-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17813046#comment-17813046 ] Bhavik Patel commented on RANGER-4076: -- [~rakeshgupta264] have you validated rangeradmin , usersync, tagsync and KMS functionality with JDK-17? > Support Java 17 for build and runtime > - > > Key: RANGER-4076 > URL: https://issues.apache.org/jira/browse/RANGER-4076 > Project: Ranger > Issue Type: New Feature > Components: admin, build-infra >Reporter: Andrew Luo >Priority: Major > Attachments: > 0001-RANGER-4076-Support-Java-17-for-build-and-runtime.patch > > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4667) Replace Nashron script engine with GraalVM
[ https://issues.apache.org/jira/browse/RANGER-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809333#comment-17809333 ] Bhavik Patel commented on RANGER-4667: -- Yes, [~madhan] I reviewed [RANGER-3970|https://issues.apache.org/jira/browse/RANGER-3970] and [RANGER-4401|https://issues.apache.org/jira/browse/RANGER-4401]. > Replace Nashron script engine with GraalVM > -- > > Key: RANGER-4667 > URL: https://issues.apache.org/jira/browse/RANGER-4667 > Project: Ranger > Issue Type: Improvement > Components: plugins, Ranger > Reporter: Bhavik Patel >Priority: Major > > Replace Nashron scrip engine with default GraalVM engine this will help in > support for JDK-17 > cc: [~madhan] / [~rdonbosco] / [~sneethir] / [~kishor.gollapalliwar] / > [~bosco] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4667) Replace Nashron scrip engine with GraalVM
[ https://issues.apache.org/jira/browse/RANGER-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4667: - Description: Replace Nashron scrip engine with default GraalVM engine this will help in support for JDK-17 cc: [~madhan] / [~rdonbosco] / [~sneethir] / [~kishor.gollapalliwar] / [~bosco] was: Replace Nashron scrip engine with default GraalVM engine this will help in support for JDK-17 cc: [~madhan] / [~rdonbosco] / [~sneethir] > Replace Nashron scrip engine with GraalVM > - > > Key: RANGER-4667 > URL: https://issues.apache.org/jira/browse/RANGER-4667 > Project: Ranger > Issue Type: Improvement > Components: plugins, Ranger > Reporter: Bhavik Patel >Priority: Major > > Replace Nashron scrip engine with default GraalVM engine this will help in > support for JDK-17 > cc: [~madhan] / [~rdonbosco] / [~sneethir] / [~kishor.gollapalliwar] / > [~bosco] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4667) Replace Nashron script engine with GraalVM
[ https://issues.apache.org/jira/browse/RANGER-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4667: - Summary: Replace Nashron script engine with GraalVM (was: Replace Nashron scrip engine with GraalVM) > Replace Nashron script engine with GraalVM > -- > > Key: RANGER-4667 > URL: https://issues.apache.org/jira/browse/RANGER-4667 > Project: Ranger > Issue Type: Improvement > Components: plugins, Ranger > Reporter: Bhavik Patel >Priority: Major > > Replace Nashron scrip engine with default GraalVM engine this will help in > support for JDK-17 > cc: [~madhan] / [~rdonbosco] / [~sneethir] / [~kishor.gollapalliwar] / > [~bosco] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4667) Replace Nashron scrip engine with GraalVM
Bhavik Patel created RANGER-4667: Summary: Replace Nashron scrip engine with GraalVM Key: RANGER-4667 URL: https://issues.apache.org/jira/browse/RANGER-4667 Project: Ranger Issue Type: Improvement Components: plugins, Ranger Reporter: Bhavik Patel Replace Nashron scrip engine with default GraalVM engine this will help in support for JDK-17 cc: [~madhan] / [~rdonbosco] / [~sneethir] -- This message was sent by Atlassian Jira (v8.20.10#820010)
