[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)
[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)
[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)
[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)
[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)
[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)
[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 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
[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)
[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)
[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)
[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)
[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)
[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)
[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)
[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)
[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)
[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)
[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)
[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)
[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)
[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=17807051#comment-17807051
]
Bhavik Patel commented on RANGER-4225:
--
Sure.
Thanks [~sercan.tekin].
> 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)
[jira] [Resolved] (RANGER-4326) Cannot renew token when multiple KMS are applied.
[
https://issues.apache.org/jira/browse/RANGER-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhavik Patel resolved RANGER-4326.
--
Resolution: Not A Problem
> Cannot renew token when multiple KMS are applied.
> -
>
> Key: RANGER-4326
> URL: https://issues.apache.org/jira/browse/RANGER-4326
> Project: Ranger
> Issue Type: Bug
> Components: kms
>Affects Versions: 2.3.0, 2.4.0
>Reporter: kirby zhou
>Priority: Major
>
> When multiple KMS are applied with kerberos. Flink on yarn can not renew
> tokens.
>
> Flink calls FileSystem.addDelegationTokens to get all tokens to renew.
> FileSystem.addDelegationTokens calls collectDelegationTokens to collect all
> tokens.
> When it calls LoadBalancingKMSClientProvider.getDelegationToken.
> LoadBalancingKMSClientProvider calls doOp to call one of N
> KMSClientProvider.getDelegationToken().
>
> When renew the token, LoadBalancingKMSClientProvider may call another
> KMSClientProvider to do op. It usually fails.
>
> FYI: have already set hadoop.kms.authentication.signer.secret.provider=file,
> and hadoop.kms.authentication.signature.secret.file="same content file".
>
> Some Sample code:
> {code:java}
> public static void main(String[] args) throws Exception {
> Configuration conf = new Configuration();
> conf.set("hadoop.security.authorization", "true");
> conf.set("hadoop.security.authentication", "kerberos");
> conf.set("dfs.data.transfer.protection", "authentication");
> conf.set("hadoop.security.key.provider.path",
> "kms://http@kms01;kms02:9292/kms");
> conf.set("dfs.client.ignore.namenode.default.kms.uri", "true");
> conf.set("fs.defaultFS", "hdfs://namenode");
> // Login with keytab
> UserGroupInformation.setConfiguration(conf);
> UserGroupInformation.loginUserFromKeytab("testuser@TESTREALM",
> "/Users/kirbyzhou/Develop/testuser.keytab");
> UserGroupInformation ugi = UserGroupInformation.getCurrentUser();
> System.out.println(UserGroupInformation.getCurrentUser().getUserName());
> // GetFS
> FileSystem fs = FileSystem.get(conf);
>
> System.out.println(((DistributedFileSystem)fs).getClient().getKeyProviderUri());
> // Renew
> for (int i = 0; i < 20; ++i) {
> Thread.sleep(200);
> System.out.printf("===pass %02d===\n", i);
> {
> System.out.println("==begin renew==");
> Credentials credentials = ugi.getCredentials();
> fs.addDelegationTokens("sa_cluster", credentials);
> for (Token token : credentials.getAllTokens()) {
> System.out.println(token);
> try {
> token.renew(conf);
> } catch (IOException e) {
> System.err.println(e);
> }
> }
> System.out.println("==end renew==");
> }
> }
> }
> {code}
> A lot of exceptions happens
> {code:java}
> ava.io.IOException: HTTP status [403], message [Forbidden], URL
> [http://kms01:9292/kms/v1/?op=RENEWDELEGATIONTOKEN&token=KgAKc2FfY2x1c3RlcgpzYV9jbHVzdGVyAIoBiYffA4WKAYmr64eFjgG_AhQ7Oo9G0Lc8IguxB0IgenAHsJ--DQZrbXMtZHRPa21zOi8vaHR0cEBrbXMwMS10aHJvbmUwMS5zZW5zb3JzZGF0YS5jbjtrbXMwMi10aHJvbmUwMS5zZW5zb3JzZGF0YS5jbjo5MjkyL2ttcw],
> exception [com.fasterxml.jackson.core.JsonParseException: Unexpected
> character ('<' (code 60)): expected a valid value (JSON String, Number,
> Array, Object or token 'null', 'true' or 'false') at [Source:
> (sun.net.www.protocol.http.HttpURLConnection$HttpInputStream); line: 1,
> column: 2]] at
> org.apache.hadoop.util.HttpExceptionUtils.validateResponse(HttpExceptionUtils.java:167)
> ~[classes/:?]at
> org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticator.doDelegationTokenOperation(DelegationTokenAuthenticator.java:318)
> ~[hadoop-common-3.3.4.jar:?] at
> org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticator.renewDelegationToken(DelegationTokenAuthenticator.java:235)
> ~[hadoop-common-3.3.4.jar:?]at
> org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticatedURL.renewDelegationToken(DelegationTokenAuthenticatedURL.java:435)
> ~[hadoop-common-3.3.4.jar:?] at
> org.apache.hadoop.crypto.key.kms.KMSClientProvider$4.run(KMSClientProvider.java:1072)
> ~[hadoop-common-3.3.4.jar:?] at
> org.apache.hadoop.crypto.key.kms.KMSClientProvider$4.run(KMSClientProvider.java:1069)
> ~[hadoop-common-3.3.4.jar:?] at
> java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_332]
> at javax.security.auth.Subject.doAs(Subject.java:422) ~[?:1.8.0_332]at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1878)
> ~[hadoop-common-3.3.4.jar:?]at
> org.apache.hado
[jira] [Commented] (RANGER-4327) Make ranger2.4 hdfs plugin compatible with hadoop 3.3.5 +
[ https://issues.apache.org/jira/browse/RANGER-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805901#comment-17805901 ] Bhavik Patel commented on RANGER-4327: -- This issue is observed as jackson-1.x version is removed in the hadoop-3.4 : [https://github.com/apache/hadoop/commit/04b6b9a87bf024e82aa50328b4994aea4268d98e#diff-635a9ebcc70f58d8ca1c55b0d78cc90064a5081d189162a432271778da3cf018] >From ranger end also we have to remove jackson-1.x version as it's vulnerable. > Make ranger2.4 hdfs plugin compatible with hadoop 3.3.5 + > - > > Key: RANGER-4327 > URL: https://issues.apache.org/jira/browse/RANGER-4327 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.3.0, 2.4.0 >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2023-07-25-17-30-18-136.png, > image-2023-07-26-13-40-10-555.png, patch3-RANGER-4327.diff > > > hadoop 3.3.5 has upgraded its jackson dependency and removed all jackson 1.x > packages, including the jackson-jaxrs jar. As a result, when starting with > the Ranger plugin enabled, Hadoop namenode fails to start due to the > inability to load jackson 1.x. > To address this issue and ensure compatibility with the Hadoop 3.3.5 upgrade, > we need to package jackson 1.x jars in the hdfs plugin as well,like the Ozone > did https://issues.apache.org/jira/browse/RANGER-2818. This will allow the > namenode to start successfully. > !image-2023-07-26-13-40-10-555.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4505) [hdfs] Error - java.lang.ClassNotFoundException: org.codehaus.jackson.jaxrs.JacksonJsonProvider
[
https://issues.apache.org/jira/browse/RANGER-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhavik Patel resolved RANGER-4505.
--
Resolution: Duplicate
> [hdfs] Error - java.lang.ClassNotFoundException:
> org.codehaus.jackson.jaxrs.JacksonJsonProvider
> ---
>
> Key: RANGER-4505
> URL: https://issues.apache.org/jira/browse/RANGER-4505
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Anatoly
>Priority: Major
>
> ranger_version 2.3.0
> After upgrading the hadoop version from 3.1. to 3.3.6 and 3.3.5, I get an
> error for hdfs -
> java.lang.ClassNotFoundException:
> org.codehaus.jackson.jaxrs.JacksonJsonProvider
>
> {code:java}
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: 2023-10-31 14:55:05,181 ERROR
> namenode.NameNode: Failed to start namenode.
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: java.lang.NoClassDefFoundError:
> org/codehaus/jackson/jaxrs/JacksonJsonProvider
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRESTClient.buildClient(RangerRESTClient.java:226)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRESTClient.getClient(RangerRESTClient.java:193)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRESTClient.get(RangerRESTClient.java:473)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.admin.client.RangerAdminRESTClient.getRangerRolesDownloadResponse(RangerAdminRESTClient.java:1340)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.admin.client.RangerAdminRESTClient.getRolesIfUpdatedWithCred(RangerAdminRESTClient.java:1202)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.admin.client.RangerAdminRESTClient.getRolesIfUpdated(RangerAdminRESTClient.java:167)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRolesProvider.loadUserGroupRolesFromAdmin(RangerRolesProvider.java:183)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRolesProvider.loadUserGroupRoles(RangerRolesProvider.java:123)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.PolicyRefresher.loadRoles(PolicyRefresher.java:495)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:144)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:243)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer.start(RangerHdfsAuthorizer.java:112)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer.start(RangerHdfsAuthorizer.java:86)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startCommonServices(FSNamesystem.java:1321)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.startCommonServices(NameNode.java:883)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:804)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:1033)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:1008)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1782)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1847)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: Caused by:
> java.lang.ClassNotFoundException:
> org.codehaus.jackson.jaxrs.JacksonJsonProvider
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> java.base/java.lang.ClassLoader.findClass(ClassLoader.java:718)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.classloader.RangerPluginClassLoader$MyClassLoader.findClass(RangerPluginClassLoader.java:316)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.classloader.RangerPluginClassLoader.loadClass(RangerPluginClassLoader.java:160)
> Oct 31 14:55:05 hadoop001 hdfs[1417563
[jira] [Commented] (RANGER-4505) [hdfs] Error - java.lang.ClassNotFoundException: org.codehaus.jackson.jaxrs.JacksonJsonProvider
[
https://issues.apache.org/jira/browse/RANGER-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805900#comment-17805900
]
Bhavik Patel commented on RANGER-4505:
--
This issue is observed as jackson-1.x version is removed in the hadoop-3.4 :
[https://github.com/apache/hadoop/commit/04b6b9a87bf024e82aa50328b4994aea4268d98e#diff-635a9ebcc70f58d8ca1c55b0d78cc90064a5081d189162a432271778da3cf018]
>From ranger end also we have to remove jackson-1.x version as it's vulnerable.
> [hdfs] Error - java.lang.ClassNotFoundException:
> org.codehaus.jackson.jaxrs.JacksonJsonProvider
> ---
>
> Key: RANGER-4505
> URL: https://issues.apache.org/jira/browse/RANGER-4505
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Anatoly
>Priority: Major
>
> ranger_version 2.3.0
> After upgrading the hadoop version from 3.1. to 3.3.6 and 3.3.5, I get an
> error for hdfs -
> java.lang.ClassNotFoundException:
> org.codehaus.jackson.jaxrs.JacksonJsonProvider
>
> {code:java}
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: 2023-10-31 14:55:05,181 ERROR
> namenode.NameNode: Failed to start namenode.
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: java.lang.NoClassDefFoundError:
> org/codehaus/jackson/jaxrs/JacksonJsonProvider
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRESTClient.buildClient(RangerRESTClient.java:226)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRESTClient.getClient(RangerRESTClient.java:193)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRESTClient.get(RangerRESTClient.java:473)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.admin.client.RangerAdminRESTClient.getRangerRolesDownloadResponse(RangerAdminRESTClient.java:1340)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.admin.client.RangerAdminRESTClient.getRolesIfUpdatedWithCred(RangerAdminRESTClient.java:1202)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.admin.client.RangerAdminRESTClient.getRolesIfUpdated(RangerAdminRESTClient.java:167)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRolesProvider.loadUserGroupRolesFromAdmin(RangerRolesProvider.java:183)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.RangerRolesProvider.loadUserGroupRoles(RangerRolesProvider.java:123)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.PolicyRefresher.loadRoles(PolicyRefresher.java:495)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:144)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:243)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer.start(RangerHdfsAuthorizer.java:112)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.authorization.hadoop.RangerHdfsAuthorizer.start(RangerHdfsAuthorizer.java:86)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startCommonServices(FSNamesystem.java:1321)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.startCommonServices(NameNode.java:883)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:804)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:1033)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:1008)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1782)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1847)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: Caused by:
> java.lang.ClassNotFoundException:
> org.codehaus.jackson.jaxrs.JacksonJsonProvider
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> java.base/java.lang.ClassLoader.findClass(ClassLoader.java:718)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> org.apache.ranger.plugin.classloader.RangerPluginClassLoader$MyClassLoader.findClass(RangerPluginClassLoader.java:316)
> Oct 31 14:55:05 hadoop001 hdfs[1417563]: at
> java.base/java.lang.ClassLoader.loadClass(Cla
[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=17805899#comment-17805899
]
Bhavik Patel commented on RANGER-4225:
--
Can you completely remove the jackson-1.x dependency from Ranger?
> 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)
[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=17805898#comment-17805898 ] Bhavik Patel commented on RANGER-3409: -- Thanks [~sercan.tekin] but we have to fir the issue. As I can see in hadoop-3.4.0 they have completely remove the support for jackson-1.x : [https://github.com/apache/hadoop/commit/04b6b9a87bf024e82aa50328b4994aea4268d98e#diff-635a9ebcc70f58d8ca1c55b0d78cc90064a5081d189162a432271778da3cf018] > 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 > > 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-3993) Upgrade okhttp dependency
[ https://issues.apache.org/jira/browse/RANGER-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797089#comment-17797089 ] Bhavik Patel commented on RANGER-3993: -- [~vikkumar] Will discuss the approach the here. Instead of defining dependencies in module's pom, use to override in parent pom and exclude from respective module's pom. For ex: for your case, exclude from admin pon and override using in parent pom? What's your thought on this? PS: Dropping my earlier review comment. Your suggestion also make sense but I thought of avoiding multiple exclusion changes so planning to go with changes at module level. And some dependency’s(version) are required for specific modules. Also, to control the dependency and their version I raised RANGER-4569. > Upgrade okhttp dependency > -- > > Key: RANGER-3993 > URL: https://issues.apache.org/jira/browse/RANGER-3993 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: 0001-RANGER-3993-Upgrade-okhttp-dependency.patch > > > Upgrade okhttp dependency -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4590) Upgrade Tomcat version to 8.5.96
[ https://issues.apache.org/jira/browse/RANGER-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4590: - Attachment: 0001-RANGER-4590-Upgrade-Tomcat-version-to-8.5.96.patch > Upgrade Tomcat version to 8.5.96 > > > Key: RANGER-4590 > URL: https://issues.apache.org/jira/browse/RANGER-4590 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: 0001-RANGER-4590-Upgrade-Tomcat-version-to-8.5.96.patch > > > Upgrade Tomcat version to 8.5.96 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4602) Upgrade Tomcat to 8.5.96 in all Ranger services
[ https://issues.apache.org/jira/browse/RANGER-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel resolved RANGER-4602. -- Resolution: Duplicate > Upgrade Tomcat to 8.5.96 in all Ranger services > --- > > Key: RANGER-4602 > URL: https://issues.apache.org/jira/browse/RANGER-4602 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > > Upgrade Tomcat to 8.5.96 in all Ranger services -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4602) Upgrade Tomcat to 8.5.96 in all Ranger services
[ https://issues.apache.org/jira/browse/RANGER-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796033#comment-17796033 ] Bhavik Patel commented on RANGER-4602: -- Hi [~sanketshelar] I already raised https://issues.apache.org/jira/browse/RANGER-4590 to upgrade tomcat version. I will raise review request in sometime. > Upgrade Tomcat to 8.5.96 in all Ranger services > --- > > Key: RANGER-4602 > URL: https://issues.apache.org/jira/browse/RANGER-4602 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > > Upgrade Tomcat to 8.5.96 in all Ranger services -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4590) Upgrade Tomcat version to 8.5.96
Bhavik Patel created RANGER-4590: Summary: Upgrade Tomcat version to 8.5.96 Key: RANGER-4590 URL: https://issues.apache.org/jira/browse/RANGER-4590 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade Tomcat version to 8.5.96 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3823) Remove commons-dbcp and commons-pool dependency
[ https://issues.apache.org/jira/browse/RANGER-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-3823: - Description: Remove commons-dbcp and commons-pool dependency as we are using Hikari-CP (was: Update commons-dbcp version to commons-dbcp2 – 2.9.0 commons-pool to commons-pool2 - 2.11.1) > Remove commons-dbcp and commons-pool dependency > > > Key: RANGER-3823 > URL: https://issues.apache.org/jira/browse/RANGER-3823 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Priority: Major > > Remove commons-dbcp and commons-pool dependency as we are using Hikari-CP -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3823) Remove commons-dbcp and commons-pool dependency
[ https://issues.apache.org/jira/browse/RANGER-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-3823: - Summary: Remove commons-dbcp and commons-pool dependency (was: Update commons-dbcp2 and commons-pool2) > Remove commons-dbcp and commons-pool dependency > > > Key: RANGER-3823 > URL: https://issues.apache.org/jira/browse/RANGER-3823 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Priority: Major > > Update commons-dbcp version to commons-dbcp2 – 2.9.0 > commons-pool to commons-pool2 - 2.11.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4583) Installation of Ranger plugin for YARN fails due to missing htrace core library
[
https://issues.apache.org/jira/browse/RANGER-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794022#comment-17794022
]
Bhavik Patel commented on RANGER-4583:
--
With which version of hadoop you are trying to test? I haven’t observed the
same error.
> Installation of Ranger plugin for YARN fails due to missing htrace core
> library
> ---
>
> Key: RANGER-4583
> URL: https://issues.apache.org/jira/browse/RANGER-4583
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.4.0
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-4583.patch
>
>
> Installation of Ranger plugin for YARN fails with following error:
> {code:java}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/htrace/core/Tracer$Builder
> at org.apache.hadoop.fs.FsTracer.get(FsTracer.java:42)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3407)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:158)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3474)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3442)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:524)
> at org.apache.hadoop.fs.Path.getFileSystem(Path.java:365)
> at
> org.apache.hadoop.security.alias.JavaKeyStoreProvider.initFileSystem(JavaKeyStoreProvider.java:89)
> at
> org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.(AbstractJavaKeyStoreProvider.java:85)
> at
> org.apache.hadoop.security.alias.JavaKeyStoreProvider.(JavaKeyStoreProvider.java:49)
> at
> org.apache.hadoop.security.alias.JavaKeyStoreProvider.(JavaKeyStoreProvider.java:41)
> at
> org.apache.hadoop.security.alias.JavaKeyStoreProvider$Factory.createProvider(JavaKeyStoreProvider.java:100)
> at
> org.apache.hadoop.security.alias.CredentialProviderFactory.getProviders(CredentialProviderFactory.java:73)
> at
> org.apache.ranger.credentialapi.CredentialReader.getDecryptedString(CredentialReader.java:74)
> at
> org.apache.ranger.credentialapi.buildks.createCredential(buildks.java:87)
> at org.apache.ranger.credentialapi.buildks.main(buildks.java:41)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.htrace.core.Tracer$Builder
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 16 more]
> Exiting plugin installation {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4581) Upgrade fasterxml jackson version to 2.16.0
Bhavik Patel created RANGER-4581: Summary: Upgrade fasterxml jackson version to 2.16.0 Key: RANGER-4581 URL: https://issues.apache.org/jira/browse/RANGER-4581 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade fasterxml jackson version to 2.16.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3823) Update commons-dbcp2 and commons-pool2
[ https://issues.apache.org/jira/browse/RANGER-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-3823: - Attachment: image-2023-12-06-12-16-05-989.png > Update commons-dbcp2 and commons-pool2 > -- > > Key: RANGER-3823 > URL: https://issues.apache.org/jira/browse/RANGER-3823 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Priority: Major > > Update commons-dbcp version to commons-dbcp2 – 2.9.0 > commons-pool to commons-pool2 - 2.11.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3823) Update commons-dbcp2 and commons-pool2
[ https://issues.apache.org/jira/browse/RANGER-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-3823: - Attachment: (was: image-2023-12-06-12-16-05-989.png) > Update commons-dbcp2 and commons-pool2 > -- > > Key: RANGER-3823 > URL: https://issues.apache.org/jira/browse/RANGER-3823 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Priority: Major > > Update commons-dbcp version to commons-dbcp2 – 2.9.0 > commons-pool to commons-pool2 - 2.11.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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=17793513#comment-17793513 ] Bhavik Patel commented on RANGER-4200: -- The latest released jquery version is 3.7.1. Can you update the patch? cc: [~Dhaval.Rajpara] / [~ni3galave] / [~mugdha.varadkar] > 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] [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=17793511#comment-17793511 ] Bhavik Patel commented on RANGER-4076: -- [~andrewluo] are you working this? > 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-4404) Audit to hdfs for orc format feature stabilisation
[
https://issues.apache.org/jira/browse/RANGER-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791532#comment-17791532
]
Bhavik Patel commented on RANGER-4404:
--
Hi [~rmani] Json to ORC conversion tool looks promising an if we processes
parallelly. Will check it out. Thanks. ===>Did you got chance to check on this?
> 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
>Assignee: 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)
[jira] [Updated] (RANGER-4570) Upgrade POI version to 5.2.5
[ https://issues.apache.org/jira/browse/RANGER-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4570: - Attachment: 0001-RANGER-4570-Upgrade-POI-version-to-5.2.5.patch > Upgrade POI version to 5.2.5 > > > Key: RANGER-4570 > URL: https://issues.apache.org/jira/browse/RANGER-4570 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: 0001-RANGER-4570-Upgrade-POI-version-to-5.2.5.patch > > > Upgrade POI version to 5.2.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4570) Upgrade POI version to 5.2.5
Bhavik Patel created RANGER-4570: Summary: Upgrade POI version to 5.2.5 Key: RANGER-4570 URL: https://issues.apache.org/jira/browse/RANGER-4570 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade POI version to 5.2.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4569) Add "ranger_home/ews/webapp/WEB-INF/lib" path in the admin-web disto file
Bhavik Patel created RANGER-4569: Summary: Add "ranger_home/ews/webapp/WEB-INF/lib" path in the admin-web disto file Key: RANGER-4569 URL: https://issues.apache.org/jira/browse/RANGER-4569 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Bhavik Patel Currently there no specific module set is present in the admin-web.xml to control dependency’s in "ranger_home/ews/webapp/WEB-INF/lib". This will help to avoid unused jar from the packaging and tar ball size will also reduce. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4568) Upgrade spring version to 5.3.31
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4568: - Attachment: 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > Upgrade spring version to 5.3.31 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade spring version to 5.3.31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4568) Upgrade spring version to 5.3.31
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4568: - Description: Upgrade spring version to 5.3.31 (was: Upgrade jetty-client to 9.4.53.v20231009) > Upgrade spring version to 5.3.31 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > > Upgrade spring version to 5.3.31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4568) Upgrade spring version to 5.3.31
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4568: - Summary: Upgrade spring version to 5.3.31 (was: Upgrade jetty-client to 9.4.53.v20231009) > Upgrade spring version to 5.3.31 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > > Upgrade jetty-client to 9.4.53.v20231009 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4568) Upgrade jetty-client to 9.4.53.v20231009
Bhavik Patel created RANGER-4568: Summary: Upgrade jetty-client to 9.4.53.v20231009 Key: RANGER-4568 URL: https://issues.apache.org/jira/browse/RANGER-4568 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade jetty-client to 9.4.53.v20231009 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4567) Upgrade woodstox and stax2api version
[ https://issues.apache.org/jira/browse/RANGER-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4567: - Attachment: 0001-RANGER-4567-Upgrade-woodstox-and-stax2api-version.patch > Upgrade woodstox and stax2api version > - > > Key: RANGER-4567 > URL: https://issues.apache.org/jira/browse/RANGER-4567 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: > 0001-RANGER-4567-Upgrade-woodstox-and-stax2api-version.patch > > > Upgrade woodstox and stax2api version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4567) Upgrade woodstox and stax2api version
Bhavik Patel created RANGER-4567: Summary: Upgrade woodstox and stax2api version Key: RANGER-4567 URL: https://issues.apache.org/jira/browse/RANGER-4567 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade woodstox and stax2api version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3993) Upgrade okhttp dependency
[ https://issues.apache.org/jira/browse/RANGER-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790469#comment-17790469 ] Bhavik Patel commented on RANGER-3993: -- As this is the transitive dependency so we can fix this in two way: 1. upgrade hadoop version so with latest version will get the updated "okhttp" dependency 2. exclude from the hadoop dependency and include them externally. As you mentioned "can't we simply update in distro that defines the runtime required libs" ==>This will only help if we are downloading the dependency(whaterver the version specified in the distro), either direct or transitive dependency otherwise that jar will not be partof the packaging. > Upgrade okhttp dependency > -- > > Key: RANGER-3993 > URL: https://issues.apache.org/jira/browse/RANGER-3993 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: 0001-RANGER-3993-Upgrade-okhttp-dependency.patch > > > Upgrade okhttp dependency -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3722) Fix Test-case failure
[ https://issues.apache.org/jira/browse/RANGER-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-3722: - Fix Version/s: 3.0.0 > Fix Test-case failure > - > > Key: RANGER-3722 > URL: https://issues.apache.org/jira/browse/RANGER-3722 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-3722-Fix-Test-case-failure.patch > > > Below Test-case fail when we use maven surefire report plugins: > > test49importPoliciesFromFileAllowingOverride(org.apache.ranger.rest.TestServiceREST) > Time elapsed: 0.157 sec <<< ERROR! > java.io.FileNotFoundException: > ./src/test/java/org/apache/ranger/rest/importPolicy/import_policy_test_file.json > (No such file or directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ranger.rest.TestServiceREST.test49importPoliciesFromFileAllowingOverride(TestServiceREST.java:1703) > > test50importPoliciesFromFileNotAllowingOverride(org.apache.ranger.rest.TestServiceREST) > Time elapsed: 0.003 sec <<< ERROR! > java.io.FileNotFoundException: > ./src/test/java/org/apache/ranger/rest/importPolicy/import_policy_test_file.json > (No such file or directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ranger.rest.TestServiceREST.test50importPoliciesFromFileNotAllowingOverride(TestServiceREST.java:1768) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4524) FIx TestRangerMetricsContainerSource class UT
[
https://issues.apache.org/jira/browse/RANGER-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789919#comment-17789919
]
Bhavik Patel commented on RANGER-4524:
--
Commit link:
https://github.com/apache/ranger/commit/c7573d06726e42ced28f3e124095ab531c93b75b
> FIx TestRangerMetricsContainerSource class UT
> -
>
> Key: RANGER-4524
> URL: https://issues.apache.org/jira/browse/RANGER-4524
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Bhavik Patel
>Assignee: Bhavik Patel
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-4524-Fix-TestRangerMetricsContainerSource-cla.patch
>
>
> Steps to reproduce:
> 1. clean .m2 repo and trigger the test-cases.
> {code:java}
> java.lang.NoClassDefFoundError: org/apache/log4j/Level at
> org.apache.ranger.metrics.source.TestRangerMetricsContainerSource.init(TestRangerMetricsContainerSource.java:46)
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Level at
> org.apache.ranger.metrics.source.TestRangerMetricsContainerSource.init(TestRangerMetricsContainerSource.java:46){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4563) Upgrade Jetty-client version to 9.4.53.v20231009
[ https://issues.apache.org/jira/browse/RANGER-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4563: - Attachment: 0001-RANGER-4563-Upgrade-Jetty-client-version-to-9.4.53.v.patch > Upgrade Jetty-client version to 9.4.53.v20231009 > > > Key: RANGER-4563 > URL: https://issues.apache.org/jira/browse/RANGER-4563 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: > 0001-RANGER-4563-Upgrade-Jetty-client-version-to-9.4.53.v.patch > > > Upgrade Jetty-client version to 9.4.53.v20231009 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4563) Upgrade Jetty-client version to 9.4.53.v20231009
Bhavik Patel created RANGER-4563: Summary: Upgrade Jetty-client version to 9.4.53.v20231009 Key: RANGER-4563 URL: https://issues.apache.org/jira/browse/RANGER-4563 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade Jetty-client version to 9.4.53.v20231009 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4441) Upgrade maven compiler plugin to 3.5
[ https://issues.apache.org/jira/browse/RANGER-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789327#comment-17789327 ] Bhavik Patel commented on RANGER-4441: -- Can someone review the patch? > Upgrade maven compiler plugin to 3.5 > > > Key: RANGER-4441 > URL: https://issues.apache.org/jira/browse/RANGER-4441 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.4.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: > 0001-RANGER-4441-Upgrade-maven-compiler-plugin-to-3.5.patch > > > Upgrade maven compiler plugin to 3.5 and current version 3.3 tried to > download log4j-1.2 jar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-3821) Update commons-codec version to 1.15
[ https://issues.apache.org/jira/browse/RANGER-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel reassigned RANGER-3821: Assignee: Bhavik Patel > Update commons-codec version to 1.15 > > > Key: RANGER-3821 > URL: https://issues.apache.org/jira/browse/RANGER-3821 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-3821-Update-commons-codec-version-to-1.15.patch > > > update commons-codec version to 1.15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
