[jira] [Commented] (RANGER-1502) Solr shutdown does not cause the audit log file to be flushed and closed.

2017-07-10 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080891#comment-16080891 ] Yan commented on RANGER-1502: - It's Solr 6.3. But can't confirm that is Solr-only because each Hadoop

[jira] [Comment Edited] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-25 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983247#comment-15983247 ] Yan edited comment on RANGER-1501 at 4/25/17 4:55 PM: -- [~coheig] 1) This jira is

[jira] [Comment Edited] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-25 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983247#comment-15983247 ] Yan edited comment on RANGER-1501 at 4/25/17 4:55 PM: -- [~coheig] 1) This jira is

[jira] [Commented] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-25 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983247#comment-15983247 ] Yan commented on RANGER-1501: - [~coheig] 1) This jira is about the HDFS is not actually flushed *when the

[jira] [Commented] (RANGER-1521) Ranger database script for mysql requires admin privileges for replicated database

2017-04-18 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973176#comment-15973176 ] Yan commented on RANGER-1521: - [~eyang] Thanks for info. Surely automated installation/deployment is

[jira] [Commented] (RANGER-1521) Ranger database script for mysql requires admin privileges for replicated database

2017-04-18 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973102#comment-15973102 ] Yan commented on RANGER-1521: - [~eyang] Not sure can follow your admin privilege arguments. Note that 1) the

[jira] [Commented] (RANGER-1521) Ranger database script for mysql requires admin privileges for replicated database

2017-04-18 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972229#comment-15972229 ] Yan commented on RANGER-1521: - A few comments: 1) There are a few workarounds to address the data corruption

[jira] [Commented] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-10 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963867#comment-15963867 ] Yan commented on RANGER-1501: - The failure to call close() was experienced by Solr Plugin as reported in

[jira] [Commented] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-08 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961924#comment-15961924 ] Yan commented on RANGER-1501: - In summary, in a true asynchorous, non-blocking execution path, the

[jira] [Commented] (RANGER-1502) Solr shutdown does not cause the audit log file to be flushed and closed.

2017-04-07 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961487#comment-15961487 ] Yan commented on RANGER-1502: - A review request has been created at https://reviews.apache.org/r/58272/.

[jira] [Commented] (RANGER-1502) Solr shutdown does not cause the audit log file to be flushed and closed.

2017-04-07 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961483#comment-15961483 ] Yan commented on RANGER-1502: - The fix is to add invocation of the shutdown hook from the close() call of the

[jira] [Created] (RANGER-1502) Solr shutdown does not cause the audit log file to be flushed and closed.

2017-04-07 Thread Yan (JIRA)
Yan created RANGER-1502: --- Summary: Solr shutdown does not cause the audit log file to be flushed and closed. Key: RANGER-1502 URL: https://issues.apache.org/jira/browse/RANGER-1502 Project: Ranger

[jira] [Commented] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-07 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961405#comment-15961405 ] Yan commented on RANGER-1501: - A review request has been created at https://reviews.apache.org/r/58268/.

[jira] [Updated] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-07 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan updated RANGER-1501: Attachment: 0001-RANGER-1501-Audit-Flush-to-HDFS-does-not-actually-ca.patch > Audit Flush to HDFS does not

[jira] [Created] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS

2017-04-07 Thread Yan (JIRA)
Yan created RANGER-1501: --- Summary: Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS Key: RANGER-1501 URL: https://issues.apache.org/jira/browse/RANGER-1501 Project: Ranger

[jira] [Comment Edited] (RANGER-1489) Solr plugin fails to get client address

2017-03-31 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951440#comment-15951440 ] Yan edited comment on RANGER-1489 at 3/31/17 6:23 PM: -- A review request is created

[jira] [Commented] (RANGER-1489) Solr plugin fails to get client address

2017-03-31 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951440#comment-15951440 ] Yan commented on RANGER-1489: - A review request is created at https://reviews.apache.org/r/58115/. I

[jira] [Commented] (RANGER-1339) DENY and ALLOW EXCLUSION do not work with YARN

2017-03-23 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938868#comment-15938868 ] Yan commented on RANGER-1339: - Any comments from the community on this issue? It seems to be a blocking one

[jira] [Updated] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty

2017-03-13 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan updated RANGER-1446: Attachment: (was: Ranger-1446.patch) > Ranger Solr Plugin does not work when the collection list in the

[jira] [Updated] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty

2017-03-13 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan updated RANGER-1446: Attachment: 0001-Ranger-1446-Ranger-Solr-Plugin-does-not-work-when-th.patch > Ranger Solr Plugin does not work

[jira] [Comment Edited] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty

2017-03-10 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905658#comment-15905658 ] Yan edited comment on RANGER-1446 at 3/10/17 8:38 PM: -- A review request is posted at

[jira] [Commented] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty

2017-03-10 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905658#comment-15905658 ] Yan commented on RANGER-1446: - A review request is posted at https://reviews.apache.org/r/57519/. Since this

[jira] [Updated] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty

2017-03-10 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan updated RANGER-1446: Attachment: Ranger-1446.patch > Ranger Solr Plugin does not work when the collection list in the request is >

[jira] [Created] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty

2017-03-10 Thread Yan (JIRA)
Yan created RANGER-1446: --- Summary: Ranger Solr Plugin does not work when the collection list in the request is empty Key: RANGER-1446 URL: https://issues.apache.org/jira/browse/RANGER-1446 Project: Ranger

[jira] [Assigned] (RANGER-1252) Policy lookup does not honor the case sensitivity flag of resources

2017-03-08 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan reassigned RANGER-1252: --- Assignee: Yan > Policy lookup does not honor the case sensitivity flag of resources >

[jira] [Updated] (RANGER-1395) LDAP group sync fails with InvalidNameException

2017-02-19 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan updated RANGER-1395: Attachment: ldap_2.patch > LDAP group sync fails with InvalidNameException >

[jira] [Commented] (RANGER-1395) LDAP group sync fails with InvalidNameException

2017-02-19 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873869#comment-15873869 ] Yan commented on RANGER-1395: - Please review a patch at https://reviews.apache.org/r/56829/ > LDAP group

[jira] [Commented] (RANGER-1395) LDAP group sync fails with InvalidNameException

2017-02-19 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873868#comment-15873868 ] Yan commented on RANGER-1395: - The result is that the LDAP groups are not synced to Ranger at all. > LDAP

[jira] [Commented] (RANGER-1395) LDAP group sync fails with InvalidNameException

2017-02-19 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873867#comment-15873867 ] Yan commented on RANGER-1395: - The problem was introduced with Ranger-893 when a short user name is added in

[jira] [Commented] (RANGER-1117) usersync pid location not configurable

2017-01-25 Thread Yan (JIRA)
[ https://issues.apache.org/jira/browse/RANGER-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838298#comment-15838298 ] Yan commented on RANGER-1117: - [~sneethiraj] Sorry, I have not kept track of the status in this direction.