[jira] [Assigned] (RANGER-2999) Ranger build is failing if you do not have already downloaded jar under ~/.m2 for calcite-linq4j-1.16.0-kylin-r2

[ https://issues.apache.org/jira/browse/RANGER-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-2999: --- Assignee: Pradeep Agrawal > Ranger build is failing if you do not have already

[jira] [Updated] (RANGER-3576) service creation is failing intermittently due to DB unique key constraint violation

[ https://issues.apache.org/jira/browse/RANGER-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3576: Attachment: (was: 0001-RANGER-3576-service-creation-is-failing-intermittent.patch) >

[jira] [Updated] (RANGER-3576) service creation is failing intermittently due to DB unique key constraint violation

[ https://issues.apache.org/jira/browse/RANGER-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3576: Attachment: 0001-RANGER-3576-service-creation-is-failing-intermittent-1.patch > service

[jira] [Updated] (RANGER-3576) service creation is failing intermittently due to DB unique key constraint violation

[ https://issues.apache.org/jira/browse/RANGER-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3576: Attachment: 0001-RANGER-3576-service-creation-is-failing-intermittent.patch > service

[jira] [Updated] (RANGER-3576) service creation is failing intermittently due to DB unique key constraint violation

[ https://issues.apache.org/jira/browse/RANGER-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3576: Summary: service creation is failing intermittently due to DB unique key constraint

[jira] [Created] (RANGER-3576) service creation is failing intermittently due to MySQLIntegrityConstraintViolationException

Pradeep Agrawal created RANGER-3576: --- Summary: service creation is failing intermittently due to MySQLIntegrityConstraintViolationException Key: RANGER-3576 URL:

[jira] [Commented] (RANGER-3550) support for using user/tag attributes in row-filter expressions and conditions

[ https://issues.apache.org/jira/browse/RANGER-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466397#comment-17466397 ] Pradeep Agrawal commented on RANGER-3550: - [~madhan]  : Please close the RR

[jira] [Commented] (RANGER-3290) ArrayIndexOutOfBoundsException if solr is down

[ https://issues.apache.org/jira/browse/RANGER-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466117#comment-17466117 ] Pradeep Agrawal commented on RANGER-3290: - [~asalamon74]  : Please close the Review request. >

[jira] [Resolved] (RANGER-3290) ArrayIndexOutOfBoundsException if solr is down

[ https://issues.apache.org/jira/browse/RANGER-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3290. - Fix Version/s: 3.0.0 Resolution: Fixed > ArrayIndexOutOfBoundsException if solr

[jira] [Commented] (RANGER-3290) ArrayIndexOutOfBoundsException if solr is down

[ https://issues.apache.org/jira/browse/RANGER-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465937#comment-17465937 ] Pradeep Agrawal commented on RANGER-3290: -

[jira] [Commented] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465277#comment-17465277 ] Pradeep Agrawal commented on RANGER-3540: - Thanks [~yInnovation]  for reviewing and guiding on

[jira] [Commented] (RANGER-2994) ranger release 2.1.0 cannot compile due to broken Kylin plugin dependency

[ https://issues.apache.org/jira/browse/RANGER-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464620#comment-17464620 ] Pradeep Agrawal commented on RANGER-2994: - [~sneethiraj]  : Can you review RANGER-3560 patch

[jira] [Commented] (RANGER-3539) Add jacoco-maven-plugin for code coverage

[ https://issues.apache.org/jira/browse/RANGER-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464497#comment-17464497 ] Pradeep Agrawal commented on RANGER-3539: - 1) Yes, jacoco need to be installed but its just to

[jira] [Updated] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3540: Attachment: RANGER-3540-6.patch > Add support to read audit logs from Amazon CloudWatch >

[jira] [Commented] (RANGER-3539) Add jacoco-maven-plugin for code coverage

[ https://issues.apache.org/jira/browse/RANGER-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464408#comment-17464408 ] Pradeep Agrawal commented on RANGER-3539: - [~bpatel]  : Can you review this ? > Add

[jira] [Updated] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3540: Attachment: RANGER-3540-5.patch > Add support to read audit logs from Amazon CloudWatch >

[jira] [Updated] (RANGER-3561) Upgrade Storm version to 1.2.4

[ https://issues.apache.org/jira/browse/RANGER-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3561: Attachment: 0001-RANGER-3561-Upgrade-Storm-version-to-1.2.4.patch > Upgrade Storm version

[jira] [Updated] (RANGER-3560) Upgrade kylin version to 2.6.6

[ https://issues.apache.org/jira/browse/RANGER-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3560: Attachment: 0001-RANGER-3560-Upgrade-kylin-version-to-2.6.6.patch > Upgrade kylin version

[jira] [Created] (RANGER-3561) Upgrade Storm version to 1.2.4

Pradeep Agrawal created RANGER-3561: --- Summary: Upgrade Storm version to 1.2.4 Key: RANGER-3561 URL: https://issues.apache.org/jira/browse/RANGER-3561 Project: Ranger Issue Type: Wish

[jira] [Created] (RANGER-3560) Upgrade kylin version to 2.6.6

Pradeep Agrawal created RANGER-3560: --- Summary: Upgrade kylin version to 2.6.6 Key: RANGER-3560 URL: https://issues.apache.org/jira/browse/RANGER-3560 Project: Ranger Issue Type: Wish

[jira] [Commented] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463776#comment-17463776 ] Pradeep Agrawal commented on RANGER-3553: - Commit link 2 :

[jira] [Assigned] (RANGER-3533) Provide sorting on columns throughout the audits result set and policy listing page.

[ https://issues.apache.org/jira/browse/RANGER-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-3533: --- Fix Version/s: 3.0.0 Assignee: Mateen Mansoori Resolution: Fixed

[jira] [Updated] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3540: Attachment: RANGER-3540-3.patch > Add support to read audit logs from Amazon CloudWatch >

[jira] [Commented] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462657#comment-17462657 ] Pradeep Agrawal commented on RANGER-3540: - [~yInnovation]  : I have updated the patch, its not

[jira] [Updated] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3540: Attachment: 0001-RANGER-3540-Add-support-to-read-audit-logs-from-Amaz-1.patch > Add

[jira] [Updated] (RANGER-3558) Remove Ranger dependency on log4j 1.X

[ https://issues.apache.org/jira/browse/RANGER-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3558: Description: if possible lets remove Ranger dependency on log4j 1.X (1.2.17) > Remove

[jira] [Created] (RANGER-3558) Remove Ranger dependency on log4j 1.X

Pradeep Agrawal created RANGER-3558: --- Summary: Remove Ranger dependency on log4j 1.X Key: RANGER-3558 URL: https://issues.apache.org/jira/browse/RANGER-3558 Project: Ranger Issue Type:

[jira] [Updated] (RANGER-3557) Upgrade to use log4j 2.17.0+ version to ensure that we are using supported version of log4j

[ https://issues.apache.org/jira/browse/RANGER-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3557: Attachment: 0001-RANGER-3557-Upgrade-to-use-log4j-2.17.0-version-to-e.patch > Upgrade to

[jira] [Assigned] (RANGER-3557) Upgrade to use log4j 2.17.0+ version to ensure that we are using supported version of log4j

[ https://issues.apache.org/jira/browse/RANGER-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-3557: --- Assignee: Pradeep Agrawal (was: Ramesh Mani) > Upgrade to use log4j 2.17.0+

[jira] [Updated] (RANGER-3557) Upgrade to use log4j 2.17.0+ version to ensure that we are using supported version of log4j

[ https://issues.apache.org/jira/browse/RANGER-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3557: Affects Version/s: 3.0.0 2.3.0 (was:

[jira] [Updated] (RANGER-3557) Upgrade to use log4j 2.17.0+ version to ensure that we are using supported version of log4j

[ https://issues.apache.org/jira/browse/RANGER-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3557: Description: Upgrade to use log4j 2.17.0+ version to ensure that we are using supported

[jira] [Updated] (RANGER-3557) Upgrade to use log4j 2.17.0+ version to ensure that we are using supported version of log4j

[ https://issues.apache.org/jira/browse/RANGER-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3557: Description: Upgrade to use log4j 2.17.0+ version to ensure that we are using supported

[jira] [Created] (RANGER-3557) Upgrade to use log4j 2.17.0+ version to ensure that we are using supported version of log4j

Pradeep Agrawal created RANGER-3557: --- Summary: Upgrade to use log4j 2.17.0+ version to ensure that we are using supported version of log4j Key: RANGER-3557 URL: https://issues.apache.org/jira/browse/RANGER-3557

[jira] [Updated] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3553: Attachment: 0002-RANGER-3553-Unit-Tests-coverage-for-UserMgr-class.patch > Unit test

[jira] [Commented] (RANGER-3545) Remove Logger Checks for Info Enabled

[ https://issues.apache.org/jira/browse/RANGER-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460642#comment-17460642 ] Pradeep Agrawal commented on RANGER-3545: - [~belugabehr]  : please close RR

[jira] [Resolved] (RANGER-3545) Remove Logger Checks for Info Enabled

[ https://issues.apache.org/jira/browse/RANGER-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3545. - Fix Version/s: 3.0.0 Resolution: Fixed

[jira] [Commented] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460520#comment-17460520 ] Pradeep Agrawal commented on RANGER-3553: - Commit link 1 :

[jira] [Commented] (RANGER-3526) policy evaluation ordering to use name as secondary sorting key

[ https://issues.apache.org/jira/browse/RANGER-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460434#comment-17460434 ] Pradeep Agrawal commented on RANGER-3526: - Commit link part-1 :

[jira] [Resolved] (RANGER-3520) Upgrade Netty version

[ https://issues.apache.org/jira/browse/RANGER-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3520. - Fix Version/s: 3.0.0 Resolution: Fixed > Upgrade Netty version >

[jira] [Updated] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3553: Attachment: 0001-RANGER-3553-Unit-test-coverage-for-XUserMgr-and-User.patch > Unit test

[jira] [Updated] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3553: Attachment: (was: 0001-RANGER-3553-Unit-test-coverage-for-XUserMgr-and-User.patch) >

[jira] [Updated] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3553: Attachment: 0001-RANGER-3553-Unit-test-coverage-for-XUserMgr-and-User.patch > Unit test

[jira] [Updated] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3553: Fix Version/s: 3.0.0 (was: 2.0.0) (was:

[jira] [Updated] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3553: Description: At present Unit Test coverage of XUserMgr is only 65%   was: Unit Test

[jira] [Updated] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

[ https://issues.apache.org/jira/browse/RANGER-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3553: Affects Version/s: (was: 1.0.0) > Unit test coverage for XUserMgr and UserMgr class >

[jira] [Created] (RANGER-3553) Unit test coverage for XUserMgr and UserMgr class

Pradeep Agrawal created RANGER-3553: --- Summary: Unit test coverage for XUserMgr and UserMgr class Key: RANGER-3553 URL: https://issues.apache.org/jira/browse/RANGER-3553 Project: Ranger

[jira] [Commented] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458886#comment-17458886 ] Pradeep Agrawal commented on RANGER-3540: - [~yInnovation] Can you review the patch please. >

[jira] [Updated] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

[ https://issues.apache.org/jira/browse/RANGER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3540: Attachment: 0001-RANGER-3540-Add-support-to-read-audit-logs-from-Amaz.patch > Add support

[jira] [Updated] (RANGER-3539) Add jacoco-maven-plugin for code coverage

[ https://issues.apache.org/jira/browse/RANGER-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3539: Attachment: 0001-RANGER-3539-Add-jacoco-maven-plugin-for-code-coverag.patch > Add

[jira] [Resolved] (RANGER-3427) Null Dereference in PublicApis.java

[ https://issues.apache.org/jira/browse/RANGER-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3427. - Fix Version/s: 3.0.0 Resolution: Fixed commit link:

[jira] [Commented] (RANGER-3290) ArrayIndexOutOfBoundsException if solr is down

[ https://issues.apache.org/jira/browse/RANGER-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456877#comment-17456877 ] Pradeep Agrawal commented on RANGER-3290: - [~asalamon74]  Please check the review comment and

[jira] [Commented] (RANGER-3490) Make policy resource signature is unique in a service

[ https://issues.apache.org/jira/browse/RANGER-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456139#comment-17456139 ] Pradeep Agrawal commented on RANGER-3490: - Patch 2 commit link :

[jira] [Commented] (RANGER-3298) Add coarse URI check for Hive Agent

[ https://issues.apache.org/jira/browse/RANGER-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456136#comment-17456136 ] Pradeep Agrawal commented on RANGER-3298: - PMD fix RR link : https://reviews.apache.org/r/73750/

[jira] [Updated] (RANGER-3539) Add jacoco-maven-plugin for code coverage

[ https://issues.apache.org/jira/browse/RANGER-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3539: Description: References : # [https://www.baeldung.com/jacoco] #

[jira] [Created] (RANGER-3540) Add support to read audit logs from Amazon CloudWatch

Pradeep Agrawal created RANGER-3540: --- Summary: Add support to read audit logs from Amazon CloudWatch Key: RANGER-3540 URL: https://issues.apache.org/jira/browse/RANGER-3540 Project: Ranger

[jira] [Updated] (RANGER-2358) Upgrade Jackson Databind to 2.9.8

[ https://issues.apache.org/jira/browse/RANGER-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-2358: Fix Version/s: 3.0.0 > Upgrade Jackson Databind to 2.9.8 >

[jira] [Created] (RANGER-3539) Add jacoco-maven-plugin for code coverage

Pradeep Agrawal created RANGER-3539: --- Summary: Add jacoco-maven-plugin for code coverage Key: RANGER-3539 URL: https://issues.apache.org/jira/browse/RANGER-3539 Project: Ranger Issue Type:

[jira] [Resolved] (RANGER-3401) Ranger Policy search based on policy guid match

[ https://issues.apache.org/jira/browse/RANGER-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3401. - Resolution: Duplicate > Ranger Policy search based on policy guid match >

[jira] [Commented] (RANGER-2967) Add support for Amazon CloudWatch Logs as an Audit Store

[ https://issues.apache.org/jira/browse/RANGER-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454941#comment-17454941 ] Pradeep Agrawal commented on RANGER-2967: - [~yInnovation]  : please close the RR

[jira] [Updated] (RANGER-3502) Make GET zone APIs accessible to authorized users only

[ https://issues.apache.org/jira/browse/RANGER-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3502: Fix Version/s: 3.0.0 > Make GET zone APIs accessible to authorized users only >

[jira] [Commented] (RANGER-2967) Add support for Amazon CloudWatch Logs as an Audit Store

[ https://issues.apache.org/jira/browse/RANGER-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454429#comment-17454429 ] Pradeep Agrawal commented on RANGER-2967: - [~yInnovation] : Can you upload and publish the patch

[jira] [Updated] (RANGER-2967) Add support for Amazon CloudWatch Logs as an Audit Store

[ https://issues.apache.org/jira/browse/RANGER-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-2967: Fix Version/s: 3.0.0 > Add support for Amazon CloudWatch Logs as an Audit Store >

[jira] [Commented] (RANGER-2967) Add support for Amazon CloudWatch Logs as an Audit Store

[ https://issues.apache.org/jira/browse/RANGER-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454379#comment-17454379 ] Pradeep Agrawal commented on RANGER-2967: - [~yInnovation]  : have resolved merge conflict and

[jira] [Updated] (RANGER-2967) Add support for Amazon CloudWatch Logs as an Audit Store

[ https://issues.apache.org/jira/browse/RANGER-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-2967: Attachment: 0001-RANGER-2967-Add-support-for-Amazon-CloudWatch-Logs-a.patch > Add support

[jira] [Commented] (RANGER-3439) Add rest api to get or delete ranger policy based on guid

[ https://issues.apache.org/jira/browse/RANGER-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452729#comment-17452729 ] Pradeep Agrawal commented on RANGER-3439: - committed the updated patch :

[jira] [Assigned] (RANGER-3528) Ranger Group creation audit is not shown during service creation

[ https://issues.apache.org/jira/browse/RANGER-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-3528: --- Assignee: Mateen Mansoori > Ranger Group creation audit is not shown during

[jira] [Resolved] (RANGER-3528) Ranger Group creation audit is not shown during service creation

[ https://issues.apache.org/jira/browse/RANGER-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3528. - Fix Version/s: 3.0.0 Resolution: Fixed

[jira] [Assigned] (RANGER-2388) db_setup is not using counTries properly

[ https://issues.apache.org/jira/browse/RANGER-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-2388: --- Assignee: Pradeep Agrawal > db_setup is not using counTries properly >

[jira] [Commented] (RANGER-2338) Ranger Internal Groups doesn't solve any problem, its an Alias

[ https://issues.apache.org/jira/browse/RANGER-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450480#comment-17450480 ] Pradeep Agrawal commented on RANGER-2338: - This helps in other permissions in ranger ui like

[jira] [Assigned] (RANGER-2338) Ranger Internal Groups doesn't solve any problem, its an Alias

[ https://issues.apache.org/jira/browse/RANGER-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-2338: --- Assignee: Pradeep Agrawal > Ranger Internal Groups doesn't solve any problem, its

[jira] [Resolved] (RANGER-2338) Ranger Internal Groups doesn't solve any problem, its an Alias

[ https://issues.apache.org/jira/browse/RANGER-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-2338. - Resolution: Information Provided > Ranger Internal Groups doesn't solve any problem,

[jira] [Assigned] (RANGER-1198) REST API: 404 while retrieving and updating a policy with a slash in the name

[ https://issues.apache.org/jira/browse/RANGER-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-1198: --- Assignee: Pradeep Agrawal > REST API: 404 while retrieving and updating a policy

[jira] [Resolved] (RANGER-1198) REST API: 404 while retrieving and updating a policy with a slash in the name

[ https://issues.apache.org/jira/browse/RANGER-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-1198. - Resolution: Not A Bug / in a ranger policy name is not supported. > REST API: 404

[jira] [Commented] (RANGER-1198) REST API: 404 while retrieving and updating a policy with a slash in the name

[ https://issues.apache.org/jira/browse/RANGER-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450465#comment-17450465 ] Pradeep Agrawal commented on RANGER-1198: - / in a ranger policy name is not supported. > REST

[jira] [Commented] (RANGER-3290) ArrayIndexOutOfBoundsException if solr is down

[ https://issues.apache.org/jira/browse/RANGER-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450463#comment-17450463 ] Pradeep Agrawal commented on RANGER-3290: - [~asalamon74]  : Please create Review request on

[jira] [Commented] (RANGER-3162) Deadlocks when trying to run parallel requests against REST api

[ https://issues.apache.org/jira/browse/RANGER-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450461#comment-17450461 ] Pradeep Agrawal commented on RANGER-3162: - Can you try again on latest code of master branch ? 

[jira] [Updated] (RANGER-3232) A Potential NPE in Issue RANGER-980

[ https://issues.apache.org/jira/browse/RANGER-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3232: Fix Version/s: (was: 2.2.0) > A Potential NPE in Issue RANGER-980 >

[jira] [Resolved] (RANGER-3230) Ranger Admin - Oracle 12 - java.sql.SQLSyntaxErrorException: ORA-00923: FROM keyword not found where expected

[ https://issues.apache.org/jira/browse/RANGER-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3230. - Resolution: Not A Bug > Ranger Admin - Oracle 12 - java.sql.SQLSyntaxErrorException:

[jira] [Assigned] (RANGER-3230) Ranger Admin - Oracle 12 - java.sql.SQLSyntaxErrorException: ORA-00923: FROM keyword not found where expected

[ https://issues.apache.org/jira/browse/RANGER-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-3230: --- Assignee: Pradeep Agrawal > Ranger Admin - Oracle 12 -

[jira] [Commented] (RANGER-3230) Ranger Admin - Oracle 12 - java.sql.SQLSyntaxErrorException: ORA-00923: FROM keyword not found where expected

[ https://issues.apache.org/jira/browse/RANGER-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450377#comment-17450377 ] Pradeep Agrawal commented on RANGER-3230: - [~theyaa] : This is already handled during

[jira] [Commented] (RANGER-3232) A Potential NPE in Issue RANGER-980

[ https://issues.apache.org/jira/browse/RANGER-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450373#comment-17450373 ] Pradeep Agrawal commented on RANGER-3232: - +1 for the patch. Please raise the review request in

[jira] [Commented] (RANGER-3410) Fix setup for non-ssl database connection

[ https://issues.apache.org/jira/browse/RANGER-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450321#comment-17450321 ] Pradeep Agrawal commented on RANGER-3410: - can you provide more details like mysql version,

[jira] [Resolved] (RANGER-3472) The createPolicy() method is not thread safe. In another word, we can create policies with same resources when creating policies concurrently

[ https://issues.apache.org/jira/browse/RANGER-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3472. - Fix Version/s: 3.0.0 Resolution: Fixed > The createPolicy() method is not thread

[jira] [Assigned] (RANGER-3472) The createPolicy() method is not thread safe. In another word, we can create policies with same resources when creating policies concurrently

[ https://issues.apache.org/jira/browse/RANGER-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-3472: --- Assignee: Pradeep Agrawal > The createPolicy() method is not thread safe. In

[jira] [Commented] (RANGER-3472) The createPolicy() method is not thread safe. In another word, we can create policies with same resources when creating policies concurrently

[ https://issues.apache.org/jira/browse/RANGER-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450307#comment-17450307 ] Pradeep Agrawal commented on RANGER-3472: - [~Xuze Yang]  : Ranger support load balancing and

[jira] [Resolved] (RANGER-3495) Ranger get role by rolename not working

[ https://issues.apache.org/jira/browse/RANGER-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3495. - Fix Version/s: 3.0.0 Resolution: Fixed Please reopen if issue is still there. >

[jira] [Commented] (RANGER-3495) Ranger get role by rolename not working

[ https://issues.apache.org/jira/browse/RANGER-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448930#comment-17448930 ] Pradeep Agrawal commented on RANGER-3495: - [~nityananda]  : i have reverted commit of

[jira] [Commented] (RANGER-3135) Ranger always ponit out "User does not have permission for this operation" when user try to query a none-exist role

[ https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17448924#comment-17448924 ] Pradeep Agrawal commented on RANGER-3135: - revert commit :

[jira] [Reopened] (RANGER-3135) Ranger always ponit out "User does not have permission for this operation" when user try to query a none-exist role

[ https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reopened RANGER-3135: - > Ranger always ponit out "User does not have permission for this operation" > when user

[jira] [Updated] (RANGER-3401) Ranger Policy search based on policy guid match

[ https://issues.apache.org/jira/browse/RANGER-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3401: Description: Ranger should provide a way to search a policy based on its guid, service

[jira] [Updated] (RANGER-3401) Ranger Policy search based on policy guid match

[ https://issues.apache.org/jira/browse/RANGER-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3401: Summary: Ranger Policy search based on policy guid match (was: Ranger Policy import

[jira] [Updated] (RANGER-3439) Add rest api to get or delete ranger policy based on guid

[ https://issues.apache.org/jira/browse/RANGER-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3439: Attachment: 0002-RANGER-3439-Add-rest-api-to-get-or-delete-ranger-pol.patch > Add rest

[jira] [Updated] (RANGER-3435) Add unique index on guid, service and zone_id column of x_policy table

[ https://issues.apache.org/jira/browse/RANGER-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3435: Attachment: 0001-RANGER-3435-Add-unique-index-on-guid-service-and-zon.patch > Add unique

[jira] [Reopened] (RANGER-3439) Add rest api to get or delete ranger policy based on guid

[ https://issues.apache.org/jira/browse/RANGER-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reopened RANGER-3439: - > Add rest api to get or delete ranger policy based on guid >

[jira] [Updated] (RANGER-3435) Add unique index on guid, service and zone_id column of x_policy table

[ https://issues.apache.org/jira/browse/RANGER-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3435: Summary: Add unique index on guid, service and zone_id column of x_policy table (was:

[jira] [Reopened] (RANGER-3435) Add unique index on guid and service id column of x_policy table

[ https://issues.apache.org/jira/browse/RANGER-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reopened RANGER-3435: - > Add unique index on guid and service id column of x_policy table >

[jira] [Resolved] (RANGER-3516) Java patch 'J10045' taking more time during upgrade.

[ https://issues.apache.org/jira/browse/RANGER-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-3516. - Resolution: Fixed Patch committed :

[jira] [Updated] (RANGER-3504) Create framework to execute DB patch dependent on Java patch.

[ https://issues.apache.org/jira/browse/RANGER-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3504: Fix Version/s: 3.0.0 > Create framework to execute DB patch dependent on Java patch. >

[jira] [Commented] (RANGER-3504) Create framework to execute DB patch dependent on Java patch.

[ https://issues.apache.org/jira/browse/RANGER-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17445687#comment-17445687 ] Pradeep Agrawal commented on RANGER-3504: - Patch committed :

[jira] [Updated] (RANGER-3493) Add unique index on service and resource_signature column of x_policy table

[ https://issues.apache.org/jira/browse/RANGER-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3493: Attachment: 0001-RANGER-3493-Add-unique-index-on-service-and-resource.patch > Add unique

<    1   2   3   4   5   6   7   8   9   10   >