[jira] [Updated] (RANGER-3302) GetAuthzEvents should check if auditProvider is null
[
https://issues.apache.org/jira/browse/RANGER-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haihui Xu updated RANGER-3302:
--
Attachment: RANGER-3302.patch
> GetAuthzEvents should check if auditProvider is null
>
>
> Key: RANGER-3302
> URL: https://issues.apache.org/jira/browse/RANGER-3302
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.1.0
>Reporter: Haihui Xu
>Assignee: Haihui Xu
>Priority: Major
> Labels: patch, performance
> Fix For: 2.2.0
>
> Attachments: RANGER-3302.patch
>
>
> Process the auditlog，need to getAuditProvider and getAuthzEvents, when
> logAuthzAudit, the code is
>if (auditProvider == null || !auditProvider.log(auditEvent)) {
> MiscUtil.logErrorMessageByInterval(LOG, "fail
> to log audit event " + auditEvent);
> }
> so, when getAuthzEvents should check auditProvider value, when auditProvider
> is null, there is no need to construct auditEvent, which is time-consuming
> and will result in the performance decline of service(kakfa broker,namenode,
> hiveserver2...)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3302) GetAuthzEvents should check if auditProvider is null
[
https://issues.apache.org/jira/browse/RANGER-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haihui Xu updated RANGER-3302:
--
Description:
Process the auditlog，need to getAuditProvider and getAuthzEvents, when
logAuthzAudit, the code is
if (auditProvider == null || !auditProvider.log(auditEvent)) {
MiscUtil.logErrorMessageByInterval(LOG, "fail
to log audit event " + auditEvent);
}
so, when getAuthzEvents should check auditProvider value, when auditProvider is
null, there is no need to construct auditEvent, which is time-consuming and
will result in the performance decline of service(kakfa broker,namenode,
hiveserver2...)
> GetAuthzEvents should check if auditProvider is null
>
>
> Key: RANGER-3302
> URL: https://issues.apache.org/jira/browse/RANGER-3302
> Project: Ranger
> Issue Type: Improvement
> Components: audit
>Affects Versions: 2.1.0
>Reporter: Haihui Xu
>Assignee: Haihui Xu
>Priority: Major
> Fix For: 2.2.0
>
>
> Process the auditlog，need to getAuditProvider and getAuthzEvents, when
> logAuthzAudit, the code is
>if (auditProvider == null || !auditProvider.log(auditEvent)) {
> MiscUtil.logErrorMessageByInterval(LOG, "fail
> to log audit event " + auditEvent);
> }
> so, when getAuthzEvents should check auditProvider value, when auditProvider
> is null, there is no need to construct auditEvent, which is time-consuming
> and will result in the performance decline of service(kakfa broker,namenode,
> hiveserver2...)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-3302) GetAuthzEvents should check if auditProvider is null
Haihui Xu created RANGER-3302: - Summary: GetAuthzEvents should check if auditProvider is null Key: RANGER-3302 URL: https://issues.apache.org/jira/browse/RANGER-3302 Project: Ranger Issue Type: Improvement Components: audit Affects Versions: 2.1.0 Reporter: Haihui Xu Assignee: Haihui Xu Fix For: 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haihui Xu reopened RANGER-2676: --- > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Critical > Labels: patch > Fix For: 1.2.1 > > Attachments: RANGER-2676.patch > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haihui Xu resolved RANGER-2676. --- Fix Version/s: 1.2.1 Resolution: Fixed > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Critical > Labels: patch > Fix For: 1.2.1 > > Attachments: RANGER-2676.patch > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2676) Before obtaining AuthzAuditEvent Object should check xasecure.audit.destination.xx value
[ https://issues.apache.org/jira/browse/RANGER-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haihui Xu updated RANGER-2676: -- Priority: Trivial (was: Critical) > Before obtaining AuthzAuditEvent Object should check > xasecure.audit.destination.xx value > > > Key: RANGER-2676 > URL: https://issues.apache.org/jira/browse/RANGER-2676 > Project: Ranger > Issue Type: Improvement > Components: audit, plugins >Affects Versions: 1.0.0, 1.1.0, 2.0.0, 1.2.0 >Reporter: Haihui Xu >Assignee: Haihui Xu >Priority: Trivial > Labels: patch > Fix For: 1.2.1 > > Attachments: RANGER-2676.patch > > > When after evalute policy and then process the auditlog，need to obtain > AuditHandler Object and AuthzAuditEvent object > (1) AuditHandler object obtained when init plugin according to the value of > xasecure.audit.destination.db/solr/hdfs/... > (2) So, obtaining AuthzAuditEvent should also according to the value of > xasecure.audit.destination.db/solr/hdfs/...,or when AuditHandler is null or > dummyHandler, constructing AuthzAuditEvent object is useless which is very > frequently called and thus result in the performance decline of service(hdfs > namenode, kakfa broker,hiveserver2...) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3300) Security Admin UI tests cannot run on Linux ARM64
[ https://issues.apache.org/jira/browse/RANGER-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354532#comment-17354532 ] Martin Tzvetanov Grigorov commented on RANGER-3300: --- https://reviews.apache.org/r/73392/ > Security Admin UI tests cannot run on Linux ARM64 > - > > Key: RANGER-3300 > URL: https://issues.apache.org/jira/browse/RANGER-3300 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 3.0.0 >Reporter: Martin Tzvetanov Grigorov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > security-admin-web UI tests fail on Linux ARM64 because they depend on > PhantomJS. > PhantomJS is not maintained since 2018 and it does not provide binary for > linux/aarch64 CPU architecture. > > I see two solutions: > 1) use [https://repo1.maven.org/maven2/com/github/liusheng/phantomjs/2.1.1/] > When building on Linux ARM64 add this library as dependency, unpack it, and > point to its aarch64 binary with PHANTOMJS_BIN=/path/to/the/unpacked/phantomjs > > 2) in my opinion a better solution would be to use headless Chromium/Firefox > instead of PhantomJS > As I said PhantomJS is not maintained since 2018 and since then there are > many changes and new features in the modern browsers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (RANGER-3300) Security Admin UI tests cannot run on Linux ARM64
[
https://issues.apache.org/jira/browse/RANGER-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354436#comment-17354436
]
Martin Tzvetanov Grigorov edited comment on RANGER-3300 at 5/31/21, 12:33 PM:
--
1) does not work because the binary is dynamically linked and it requires extra
libraries to be pre-installed on the build machines:
{code:java}
$ ./target/phantomjs-2.1.1-linux-aarch64/bin/phantomjs --version
./target/phantomjs-2.1.1-linux-aarch64/bin/phantomjs: error while loading
shared libraries: libicui18n.so.55: cannot open shared object file: No such
file or directory{code}
Using Ubuntu's phantomjs (for aarch64) also fails with:
{code:java}
$ phantomjs --version
qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt
platform plugin "xcb" in "" even though it was found. This application failed
to start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem. Available platform plugins are: eglfs,
linuxfb, minimal, minimalegl, offscreen, vnc, xcb. PhantomJS has crashed.
Please read the bug reporting guide at
and file a bug report. fish:
“phantomjs --version” terminated by signal SIGABRT (Abort)
{code}
was (Author: mgrigorov):
1) does not work because the binary is dynamically linked and it requires extra
libraries to be pre-installed on the build machines:
{code:java}
$ ./target/phantomjs-2.1.1-linux-aarch64/bin/phantomjs --version
./target/phantomjs-2.1.1-linux-aarch64/bin/phantomjs: error while loading
shared libraries: libicui18n.so.55: cannot open shared object file: No such
file or directory{code}
Using Ubuntu's phantomjs (for aarch64) also fails with:
{code:java}
$ phantomjs --version qt.qpa.xcb: could not connect to display qt.qpa.plugin:
Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem. Available
platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
PhantomJS has crashed. Please read the bug reporting guide at
and file a bug report. fish:
“phantomjs --version” terminated by signal SIGABRT (Abort)
{code}
> Security Admin UI tests cannot run on Linux ARM64
> -
>
> Key: RANGER-3300
> URL: https://issues.apache.org/jira/browse/RANGER-3300
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 3.0.0
>Reporter: Martin Tzvetanov Grigorov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> security-admin-web UI tests fail on Linux ARM64 because they depend on
> PhantomJS.
> PhantomJS is not maintained since 2018 and it does not provide binary for
> linux/aarch64 CPU architecture.
>
> I see two solutions:
> 1) use [https://repo1.maven.org/maven2/com/github/liusheng/phantomjs/2.1.1/]
> When building on Linux ARM64 add this library as dependency, unpack it, and
> point to its aarch64 binary with PHANTOMJS_BIN=/path/to/the/unpacked/phantomjs
>
> 2) in my opinion a better solution would be to use headless Chromium/Firefox
> instead of PhantomJS
> As I said PhantomJS is not maintained since 2018 and since then there are
> many changes and new features in the modern browsers
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-3300) Security Admin UI tests cannot run on Linux ARM64
[
https://issues.apache.org/jira/browse/RANGER-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354436#comment-17354436
]
Martin Tzvetanov Grigorov commented on RANGER-3300:
---
1) does not work because the binary is dynamically linked and it requires extra
libraries to be pre-installed on the build machines:
{code:java}
$ ./target/phantomjs-2.1.1-linux-aarch64/bin/phantomjs --version
./target/phantomjs-2.1.1-linux-aarch64/bin/phantomjs: error while loading
shared libraries: libicui18n.so.55: cannot open shared object file: No such
file or directory{code}
Using Ubuntu's phantomjs (for aarch64) also fails with:
{code:java}
$ phantomjs --version qt.qpa.xcb: could not connect to display qt.qpa.plugin:
Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem. Available
platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
PhantomJS has crashed. Please read the bug reporting guide at
and file a bug report. fish:
“phantomjs --version” terminated by signal SIGABRT (Abort)
{code}
> Security Admin UI tests cannot run on Linux ARM64
> -
>
> Key: RANGER-3300
> URL: https://issues.apache.org/jira/browse/RANGER-3300
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 3.0.0
>Reporter: Martin Tzvetanov Grigorov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> security-admin-web UI tests fail on Linux ARM64 because they depend on
> PhantomJS.
> PhantomJS is not maintained since 2018 and it does not provide binary for
> linux/aarch64 CPU architecture.
>
> I see two solutions:
> 1) use [https://repo1.maven.org/maven2/com/github/liusheng/phantomjs/2.1.1/]
> When building on Linux ARM64 add this library as dependency, unpack it, and
> point to its aarch64 binary with PHANTOMJS_BIN=/path/to/the/unpacked/phantomjs
>
> 2) in my opinion a better solution would be to use headless Chromium/Firefox
> instead of PhantomJS
> As I said PhantomJS is not maintained since 2018 and since then there are
> many changes and new features in the modern browsers
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [ranger] martin-g opened a new pull request #102: RANGER-3300 Use headless Chromium instead of PhantomJS
martin-g opened a new pull request #102: URL: https://github.com/apache/ranger/pull/102 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Description: There is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name (was: !Screen Shot 2021-05-25 at 3.10.46 AM.png! there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name) > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: Screen Shot 2021-05-25 at 3.10.46 AM.png > > > There is ranger policy with a big storage url , and in admin audit policy > detail table, fields are not correctly formatted, which gives impression that > storage-url exclude is set to > qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Attachment: Screen Shot 2021-05-25 at 3.10.46 AM.png > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: Screen Shot 2021-05-25 at 3.10.46 AM.png > > > there is ranger policy with a big storage url , and in admin audit policy > detail table, fields are not correctly formatted, which gives impression that > storage-url exclude is set to > qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
[ https://issues.apache.org/jira/browse/RANGER-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Galave updated RANGER-3301: - Description: !Screen Shot 2021-05-25 at 3.10.46 AM.png! there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name (was: there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name) > [UI] in admin audit log for Storage url policy details filed table is not > correctly formatted if storage url is big. > > > Key: RANGER-3301 > URL: https://issues.apache.org/jira/browse/RANGER-3301 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Nitin Galave >Assignee: Nitin Galave >Priority: Major > Attachments: Screen Shot 2021-05-25 at 3.10.46 AM.png > > > !Screen Shot 2021-05-25 at 3.10.46 AM.png! there is ranger policy with a big > storage url , and in admin audit policy detail table, fields are not > correctly formatted, which gives impression that storage-url exclude is set > to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3301) [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big.
Nitin Galave created RANGER-3301: Summary: [UI] in admin audit log for Storage url policy details filed table is not correctly formatted if storage url is big. Key: RANGER-3301 URL: https://issues.apache.org/jira/browse/RANGER-3301 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Nitin Galave Assignee: Nitin Galave there is ranger policy with a big storage url , and in admin audit policy detail table, fields are not correctly formatted, which gives impression that storage-url exclude is set to qhczjh.root.hwx.site:2181/table_2021_05_24_21_24_31_194441/:key,cf:name -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3300) Security Admin UI tests cannot run on Linux ARM64
[ https://issues.apache.org/jira/browse/RANGER-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354328#comment-17354328 ] Martin Tzvetanov Grigorov commented on RANGER-3300: --- Ranger devs: Which approach do you prefer ? > Security Admin UI tests cannot run on Linux ARM64 > - > > Key: RANGER-3300 > URL: https://issues.apache.org/jira/browse/RANGER-3300 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 3.0.0 >Reporter: Martin Tzvetanov Grigorov >Priority: Minor > > security-admin-web UI tests fail on Linux ARM64 because they depend on > PhantomJS. > PhantomJS is not maintained since 2018 and it does not provide binary for > linux/aarch64 CPU architecture. > > I see two solutions: > 1) use [https://repo1.maven.org/maven2/com/github/liusheng/phantomjs/2.1.1/] > When building on Linux ARM64 add this library as dependency, unpack it, and > point to its aarch64 binary with PHANTOMJS_BIN=/path/to/the/unpacked/phantomjs > > 2) in my opinion a better solution would be to use headless Chromium/Firefox > instead of PhantomJS > As I said PhantomJS is not maintained since 2018 and since then there are > many changes and new features in the modern browsers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3300) Security Admin UI tests cannot run on Linux ARM64
Martin Tzvetanov Grigorov created RANGER-3300: - Summary: Security Admin UI tests cannot run on Linux ARM64 Key: RANGER-3300 URL: https://issues.apache.org/jira/browse/RANGER-3300 Project: Ranger Issue Type: Bug Components: admin Affects Versions: 3.0.0 Reporter: Martin Tzvetanov Grigorov security-admin-web UI tests fail on Linux ARM64 because they depend on PhantomJS. PhantomJS is not maintained since 2018 and it does not provide binary for linux/aarch64 CPU architecture. I see two solutions: 1) use [https://repo1.maven.org/maven2/com/github/liusheng/phantomjs/2.1.1/] When building on Linux ARM64 add this library as dependency, unpack it, and point to its aarch64 binary with PHANTOMJS_BIN=/path/to/the/unpacked/phantomjs 2) in my opinion a better solution would be to use headless Chromium/Firefox instead of PhantomJS As I said PhantomJS is not maintained since 2018 and since then there are many changes and new features in the modern browsers -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3243) Build fails on JDK 8 and 11
[
https://issues.apache.org/jira/browse/RANGER-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354296#comment-17354296
]
Martin Tzvetanov Grigorov commented on RANGER-3243:
---
JDK: build 11.0.11+9-Ubuntu-0ubuntu2.20.04
{code:java}
[INFO] Apache Ranger Distribution . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:18 min
[INFO] Finished at: 2021-05-31T09:26:59+01:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on
project ranger-kms: Compilation failure
[ERROR]
/home/ubuntu/git/apache/ranger/kms/src/main/java/org/apache/hadoop/crypto/key/RangerSafenetKeySecure.java:[72,49]
error: incompatible types: String cannot be converted to Config
[ERROR]
[ERROR] -> [Help 1]
{code}
This is fixed with
https://github.com/apache/ranger/pull/96/files#diff-bc06b20fcb395424f2541febad5ba131085d2959eb99335da036f390188dd5eeR72
> Build fails on JDK 8 and 11
> ---
>
> Key: RANGER-3243
> URL: https://issues.apache.org/jira/browse/RANGER-3243
> Project: Ranger
> Issue Type: Task
> Components: build-infra
>Reporter: Martin Tzvetanov Grigorov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The build of current master branch fails -
> [https://travis-ci.com/github/apache/ranger/builds/223139469]
> There are several issues:
> [Issue 1|https://reviews.apache.org/r/73281/bugs/1/])
> org.apache.ranger.authorization.presto.authorizer.RangerSystemAccessControlFactory
> was not able to import com.google.common.base.Throwables.throwIfUnchecked
> because it was coming from an old copy of Guava's Throwables shaded in
> hive-exec.
> By replacing hive-exec with orc-core in agents-audit module all depending
> modules use their preferred version of Guava (26.0-jre)
> [Issue 2|https://reviews.apache.org/r/73281/bugs/2/])
> RangerSafenetKeySecure.java uses directly sun.security.pkcs11.SunPKCS11 - a
> class that is not available in Java 9+ and this breaks the compilation.
> This should use reflection to load SunPKCS11 class dynamically.
> [Issue 3|https://reviews.apache.org/r/73281/bugs/3/]) JAXB is no more part of
> JDK 11+
> [Issue 4|https://reviews.apache.org/r/73281/bugs/4/]) JUnit 4
> Assert.assertThat() is deprecated in favour of Hamcrest's
> MatcherAssert.assertThat(). This fixes a compilation issue with JDK11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-3243) Build fails on JDK 8 and 11
[ https://issues.apache.org/jira/browse/RANGER-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354279#comment-17354279 ] Martin Tzvetanov Grigorov commented on RANGER-3243: --- I was not able to find the problem, so I just disabled the example-distro module and the build passed for JDK 1.8. The only problem is with the UI build for security-admin because PhantomJS project does not provide ARM64 binaries. I will create a separate issue for this! > Build fails on JDK 8 and 11 > --- > > Key: RANGER-3243 > URL: https://issues.apache.org/jira/browse/RANGER-3243 > Project: Ranger > Issue Type: Task > Components: build-infra >Reporter: Martin Tzvetanov Grigorov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The build of current master branch fails - > [https://travis-ci.com/github/apache/ranger/builds/223139469] > There are several issues: > [Issue 1|https://reviews.apache.org/r/73281/bugs/1/]) > org.apache.ranger.authorization.presto.authorizer.RangerSystemAccessControlFactory > was not able to import com.google.common.base.Throwables.throwIfUnchecked > because it was coming from an old copy of Guava's Throwables shaded in > hive-exec. > By replacing hive-exec with orc-core in agents-audit module all depending > modules use their preferred version of Guava (26.0-jre) > [Issue 2|https://reviews.apache.org/r/73281/bugs/2/]) > RangerSafenetKeySecure.java uses directly sun.security.pkcs11.SunPKCS11 - a > class that is not available in Java 9+ and this breaks the compilation. > This should use reflection to load SunPKCS11 class dynamically. > [Issue 3|https://reviews.apache.org/r/73281/bugs/3/]) JAXB is no more part of > JDK 11+ > [Issue 4|https://reviews.apache.org/r/73281/bugs/4/]) JUnit 4 > Assert.assertThat() is deprecated in favour of Hamcrest's > MatcherAssert.assertThat(). This fixes a compilation issue with JDK11. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3243) Build fails on JDK 8 and 11
[
https://issues.apache.org/jira/browse/RANGER-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354272#comment-17354272
]
Martin Tzvetanov Grigorov commented on RANGER-3243:
---
[~pradeep] I am trying to build Ranger on Linux ARM64
OS: Ubuntu 20.04.2
JDK: 1.8.0_292-8u292-b10-0ubuntu1~20.04-b10
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Ranger: current master (3af3415f6fae4f655d46ffd80dd8c2ad1c8c1dec)
Maven command: mvn clean install -DskipJSTests
Today's build fails with:
{code:java}
[INFO] --- maven-assembly-plugin:2.6:single (default) @ ranger-examples-distro
---
[INFO] Reading assembly descriptor: src/main/assembly/sampleapp.xml
[INFO] Reading assembly descriptor: src/main/assembly/plugin-sampleapp.xml
[INFO] Reading assembly descriptor: src/main/assembly/sample-client.xml
[WARNING] The following patterns were never triggered in this artifact
inclusion filter:
o 'org.apache.ranger:sampleapp'[INFO]
[INFO] Reactor Summary for Ranger Examples - SampleApp 3.0.0-SNAPSHOT:
[INFO]
[INFO] Ranger Examples - SampleApp SUCCESS [ 4.472 s]
[INFO] Ranger Examples - Ranger Plugin for SampleApp .. SUCCESS [ 4.626 s]
[INFO] sample-client .. SUCCESS [ 2.798 s]
[INFO] Apache Ranger Examples Distribution FAILURE [ 1.291 s]
[INFO] Ranger Tools ... SKIPPED
[INFO] Atlas Security Plugin .. SKIPPED
[INFO] SchemaRegistry Security Plugin . SKIPPED
[INFO] Sqoop Security Plugin .. SKIPPED
[INFO] Sqoop Security Plugin Shim . SKIPPED
[INFO] Kylin Security Plugin .. SKIPPED
[INFO] Kylin Security Plugin Shim . SKIPPED
[INFO] Presto Security Plugin . SKIPPED
[INFO] Presto Security Plugin Shim SKIPPED
[INFO] Elasticsearch Security Plugin Shim . SKIPPED
[INFO] Elasticsearch Security Plugin .. SKIPPED
[INFO] Apache Ranger Distribution . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 13.817 s
[INFO] Finished at: 2021-05-31T08:51:11+01:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default) on project
ranger-examples-distro: Failed to create assembly: Error creating assembly
archive sampleapp: You must set at least one file. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
{code}
I will try to solve this problem and finish the build.
After that I will paste the Maven output for JDK 11!
> Build fails on JDK 8 and 11
> ---
>
> Key: RANGER-3243
> URL: https://issues.apache.org/jira/browse/RANGER-3243
> Project: Ranger
> Issue Type: Task
> Components: build-infra
>Reporter: Martin Tzvetanov Grigorov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The build of current master branch fails -
> [https://travis-ci.com/github/apache/ranger/builds/223139469]
> There are several issues:
> [Issue 1|https://reviews.apache.org/r/73281/bugs/1/])
> org.apache.ranger.authorization.presto.authorizer.RangerSystemAccessControlFactory
> was not able to import com.google.common.base.Throwables.throwIfUnchecked
> because it was coming from an old copy of Guava's Throwables shaded in
> hive-exec.
> By replacing hive-exec with orc-core in agents-audit module all depending
> modules use their preferred version of Guava (26.0-jre)
> [Issue 2|https://reviews.apache.org/r/73281/bugs/2/])
> RangerSafenetKeySecure.java uses directly sun.security.pkcs11.SunPKCS11 - a
> class that is not available in Java 9+ and this breaks the compilation.
> This should use reflection to load SunPKCS11 class dynamically.
> [Issue 3|https://reviews.apache.org/r/73281/bugs/3/]) JAXB is no more part of
> JDK 11+
> [Issue 4|https://reviews.apache.org/r/73281/bugs/4/]) JUnit 4
> Assert.assertThat() is deprecated in favour of Hamcrest's
> MatcherAssert.assertThat(). This fixes a compilation issue with JDK11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
