[jira] [Created] (RANGER-1473) There is invalid clause in the installer for Install and Configure Solr for Ranger Audits

peng.jianhua created RANGER-1473: Summary: There is invalid clause in the installer for Install and Configure Solr for Ranger Audits Key: RANGER-1473 URL: https://issues.apache.org/jira/browse/RANGER-1473

[jira] [Updated] (RANGER-1473) There is invalid clause in the installer for Install and Configure Solr for Ranger Audits

[ https://issues.apache.org/jira/browse/RANGER-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1473: - Attachment: 0001-RANGER-1473-There-is-invalid-clause-in-the-installer.patch > There is invalid

[jira] [Updated] (RANGER-1473) There is invalid clause in the installer for Install and Configure Solr for Ranger Audits

[ https://issues.apache.org/jira/browse/RANGER-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1473: - Description: The installer used the RANGER_AUDITS_DATA_FOLDER attribute value in Install and

[jira] [Created] (RANGER-1467) The password is not set after the user is created by install program during installing Ranger Policy Admin. We should set password like db user.

peng.jianhua created RANGER-1467: Summary: The password is not set after the user is created by install program during installing Ranger Policy Admin. We should set password like db user. Key: RANGER-1467 URL:

[jira] [Created] (RANGER-1470) The logic of the solr_for_audit_setup installer parsing the properites file is inconsistent with the other installers. It treated these attributes as environment variabl

peng.jianhua created RANGER-1470: Summary: The logic of the solr_for_audit_setup installer parsing the properites file is inconsistent with the other installers. It treated these attributes as environment variable. There are security risks in

[jira] [Created] (RANGER-1508) In the non English environment, the login fails, the browser returns garbled, we need to log in to support the internationalization of the function to solve this problem

peng.jianhua created RANGER-1508: Summary: In the non English environment, the login fails, the browser returns garbled, we need to log in to support the internationalization of the function to solve this problem Key:

[jira] [Updated] (RANGER-1508) In the non English environment, the login fails, the browser returns garbled, we need to log in to support the internationalization of the function to solve this problem

[ https://issues.apache.org/jira/browse/RANGER-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1508: - Priority: Critical (was: Major) > In the non English environment, the login fails, the browser

[jira] [Updated] (RANGER-1508) The browser return garbled when we logined ranger security admin in non-english os. we need support the internationalization function to solve this problem.

[ https://issues.apache.org/jira/browse/RANGER-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1508: - Summary: The browser return garbled when we logined ranger security admin in non-english os. we

[jira] [Updated] (RANGER-1508) In the non English environment, the login fails, the browser returns garbled, we need to log in to support the internationalization of the function to solve this problem

[ https://issues.apache.org/jira/browse/RANGER-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1508: - Attachment: 0001-RANGER-1508-support-internationalization.patch > In the non English

[jira] [Updated] (RANGER-1508) The browser returns garbled when we login ranger security admin in non-English environment. We need support the internationalization function to solve this problem.

[ https://issues.apache.org/jira/browse/RANGER-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1508: - Attachment: 0001-RANGER-1508-support-internationalization.patch > The browser returns garbled

[jira] [Updated] (RANGER-1508) The browser returns garbled when we login ranger security admin in non-English environment. We need support the internationalization function to solve this problem.

[ https://issues.apache.org/jira/browse/RANGER-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1508: - Attachment: (was: 0001-RANGER-1508-support-internationalization.patch) > The browser returns

[jira] [Created] (RANGER-1515) Run updatepolicymgrpassword.sh and updatepolicymgrpassword.py to update policy mgr password failed.

peng.jianhua created RANGER-1515: Summary: Run updatepolicymgrpassword.sh and updatepolicymgrpassword.py to update policy mgr password failed. Key: RANGER-1515 URL:

[jira] [Updated] (RANGER-1515) Run updatepolicymgrpassword.sh and updatepolicymgrpassword.py to update policy mgr password failed.

[ https://issues.apache.org/jira/browse/RANGER-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1515: - Attachment: 0001-RANGER-1515-Run-updatepolicymgrpassword.sh-and-updat.patch > Run

[jira] [Updated] (RANGER-1525) Some users hope that the execute programs and install configuration file of the Ranger Admin can be deployed separately when they integrate Ranger into the big data plat

[ https://issues.apache.org/jira/browse/RANGER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1525: - Attachment: 0001-RANGER-1525-Some-users-hope-that-the-execute-program.patch > Some users hope

[jira] [Updated] (RANGER-1525) Some users hope that the execute programs and install configuration file of the Ranger Admin can be deployed separately when they integrate Ranger into the big data plat

[ https://issues.apache.org/jira/browse/RANGER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1525: - Summary: Some users hope that the execute programs and install configuration file of the Ranger

[jira] [Created] (RANGER-1540) Log is very important for big data platform. The main purpose of log analysis is that we need to know who is running the service, in which machine running service, which

peng.jianhua created RANGER-1540: Summary: Log is very important for big data platform. The main purpose of log analysis is that we need to know who is running the service, in which machine running service, which service out of the problem. The

[jira] [Updated] (RANGER-1540) Log is very important for big data platform. The main purpose of log analysis is that we need to know who is running the service, in which machine running service, which

[ https://issues.apache.org/jira/browse/RANGER-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1540: - Description: Log is very important for big data platform. The main purpose of log analysis is

[jira] [Created] (RANGER-1449) There is logical inconsistency for RANGER_PID_DIR_PATH in security admin

peng.jianhua created RANGER-1449: Summary: There is logical inconsistency for RANGER_PID_DIR_PATH in security admin Key: RANGER-1449 URL: https://issues.apache.org/jira/browse/RANGER-1449 Project:

[jira] [Updated] (RANGER-1452) The install program used SOLR_RANGER_COLLECTION attribute value in Install and Configure Solr for Ranger Audits. But there is no corresponding setting in install.propert

[ https://issues.apache.org/jira/browse/RANGER-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1452: - Attachment: 0001-RANGER-1452-The-install-program-used-SOLR_RANGER_COL.patch > The install

[jira] [Created] (RANGER-1452) The install program used SOLR_RANGER_COLLECTION attribute value in Install and Configure Solr for Ranger Audits. But there is no corresponding setting in install.propert

peng.jianhua created RANGER-1452: Summary: The install program used SOLR_RANGER_COLLECTION attribute value in Install and Configure Solr for Ranger Audits. But there is no corresponding setting in install.properties. So the user can only used

[jira] [Updated] (RANGER-1525) Some users hope that the execute programs and configurations of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or busi

[ https://issues.apache.org/jira/browse/RANGER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1525: - Description: Some users hope that the execute programs and configurations of the Ranger Admin

[jira] [Created] (RANGER-1525) Some user hope that the execute programs and configurations of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or busin

peng.jianhua created RANGER-1525: Summary: Some user hope that the execute programs and configurations of the Ranger Admin can be deployed separately when they integrate Ranger into the big data platform or business systems.

[jira] [Updated] (RANGER-1723) The Ranger doesn't support solr6. In the HttpSolrClient class of solr6, the setMaxRetries function has been removed, which causes ranger to fail to compile.

[ https://issues.apache.org/jira/browse/RANGER-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1723: - Description: In the HttpSolrClient class of solr5, the setMaxRetries function is deprecated,

[jira] [Created] (RANGER-1723) The Ranger doesn't support solr6. In the HttpSolrClient class of solr6, the setMaxRetries function has been removed, which causes ranger to fail to compile.

peng.jianhua created RANGER-1723: Summary: The Ranger doesn't support solr6. In the HttpSolrClient class of solr6, the setMaxRetries function has been removed, which causes ranger to fail to compile. Key: RANGER-1723

[jira] [Updated] (RANGER-1723) The Ranger doesn't support solr6. In the HttpSolrClient class of solr6, the setMaxRetries function has been removed, which causes ranger to fail to compile.

[ https://issues.apache.org/jira/browse/RANGER-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1723: - Attachment: 0001-RANGER-1723-The-Ranger-doesn-t-support-solr6.-In-the.patch > The Ranger doesn't

[jira] [Created] (RANGER-1694) Execute 007-updateBlankPolicyName.sql failed in some mysql environment, which will cause ranger-admin start fail.

peng.jianhua created RANGER-1694: Summary: Execute 007-updateBlankPolicyName.sql failed in some mysql environment, which will cause ranger-admin start fail. Key: RANGER-1694 URL:

[jira] [Updated] (RANGER-1688) The version file did not exist in ranger-1.0.0-SNAPSHOT-kms.tar.gz. The result was that the VERSION variable can only get a fixed 0.5.0 value when installed ranger kms.

[ https://issues.apache.org/jira/browse/RANGER-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1688: - Attachment: 0001-RANGER-1688-The-version-file-did-not-exist-in-ranger.patch > The version file

[jira] [Created] (RANGER-1688) The version file did not exist in ranger-1.0.0-SNAPSHOT-kms.tar.gz. The result was that the VERSION variable can only get a fixed 0.5.0 value when installed ranger kms.

peng.jianhua created RANGER-1688: Summary: The version file did not exist in ranger-1.0.0-SNAPSHOT-kms.tar.gz. The result was that the VERSION variable can only get a fixed 0.5.0 value when installed ranger kms. Key: RANGER-1688

[jira] [Updated] (RANGER-1678) In different places to achieve the same function using repeat codes, new issue is perhaps generated when these functions are modified.

[ https://issues.apache.org/jira/browse/RANGER-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1678: - Attachment: 0001-RANGER-1678-In-different-places-to-achieve-the-same-.patch > In different

[jira] [Updated] (RANGER-1678) In different places to achieve the same function using repeat codes, new issue is perhaps generated when these functions are modified.

[ https://issues.apache.org/jira/browse/RANGER-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1678: - Attachment: 0001-RANGER-1678-In-different-places-to-achieve-the-same-.patch > In different

[jira] [Created] (RANGER-1686) Log file name format of usersync and security admin should be consistent.

peng.jianhua created RANGER-1686: Summary: Log file name format of usersync and security admin should be consistent. Key: RANGER-1686 URL: https://issues.apache.org/jira/browse/RANGER-1686 Project:

[jira] [Created] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.

peng.jianhua created RANGER-1690: Summary: Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list. Key: RANGER-1690 URL:

[jira] [Updated] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.

[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1690: - Attachment: 0001-RANGER-1690-Ranger-usersync-created-error-users.-Ran.patch > Ranger usersync

[jira] [Updated] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.

[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1690: - Description: The ranger.usersync.unix.minGroupId is not set default value. Like

[jira] [Created] (RANGER-1692) Similar to RANGER-1540, the Ranger kms should also support the same new feature.

peng.jianhua created RANGER-1692: Summary: Similar to RANGER-1540, the Ranger kms should also support the same new feature. Key: RANGER-1692 URL: https://issues.apache.org/jira/browse/RANGER-1692

[jira] [Updated] (RANGER-1692) Similar to RANGER-1540, the Ranger kms should also support the same new feature.

[ https://issues.apache.org/jira/browse/RANGER-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1692: - Attachment: 0001-RANGER-1692-Similar-to-RANGER-1540-the-Ranger-kms-sh.patch > Similar to

[jira] [Created] (RANGER-1693) The pidf's assignment logic in ranger-kms-initd should be consistent with the pidf's assignment logic in ranger-kms

peng.jianhua created RANGER-1693: Summary: The pidf's assignment logic in ranger-kms-initd should be consistent with the pidf's assignment logic in ranger-kms Key: RANGER-1693 URL:

[jira] [Updated] (RANGER-1693) The pidf's assignment logic in ranger-kms-initd should be consistent with the pidf's assignment logic in ranger-kms

[ https://issues.apache.org/jira/browse/RANGER-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1693: - Attachment: 0001-RANGER-1693-The-pidf-s-assignment-logic-in-ranger-km.patch > The pidf's

[jira] [Updated] (RANGER-1693) The pidf's assignment logic in ranger-kms-initd should be consistent with the pidf's assignment logic in ranger-kms

[ https://issues.apache.org/jira/browse/RANGER-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1693: - Description: The pidf's assignment logic in ranger-kms-initd is as following:

[jira] [Updated] (RANGER-1681) Now ranger's kerberos configuration item relies directly on the configuration of the hadoop component. When the HDFS opens other functions such as HA, the test connectio

[ https://issues.apache.org/jira/browse/RANGER-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1681: - Attachment: 0001-RANGER-1681.patch > Now ranger's kerberos configuration item relies directly on

[jira] [Comment Edited] (RANGER-1681) Now ranger's kerberos configuration item relies directly on the configuration of the hadoop component. When the HDFS opens other functions such as HA, the test co

[ https://issues.apache.org/jira/browse/RANGER-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079980#comment-16079980 ] peng.jianhua edited comment on RANGER-1681 at 7/10/17 7:44 AM: --- Hi

[jira] [Commented] (RANGER-1681) Now ranger's kerberos configuration item relies directly on the configuration of the hadoop component. When the HDFS opens other functions such as HA, the test connect

[ https://issues.apache.org/jira/browse/RANGER-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079980#comment-16079980 ] peng.jianhua commented on RANGER-1681: -- Hi [~vperiasamy], you are right. It is one of the ways to

[jira] [Updated] (RANGER-1698) Write audit log to solr failure.

[ https://issues.apache.org/jira/browse/RANGER-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1698: - Attachment: 0001-RANGER-1698-Write-audit-log-to-solr-failure.patch > Write audit log to solr

[jira] [Updated] (RANGER-1698) Write audit log to solr failure.

[ https://issues.apache.org/jira/browse/RANGER-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1698: - Description: Plugin writed audit log to solr failure because of the lack of noggit-0.6.jar in

[jira] [Updated] (RANGER-1698) Write audit log to solr failure.

[ https://issues.apache.org/jira/browse/RANGER-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1698: - Priority: Critical (was: Major) > Write audit log to solr failure. >

[jira] [Updated] (RANGER-1709) kms test case write logs to log file

[ https://issues.apache.org/jira/browse/RANGER-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1709: - Description: kms test case support writing logs to log file. (was: kms test case support

[jira] [Updated] (RANGER-1709) kms test case write logs to log file

[ https://issues.apache.org/jira/browse/RANGER-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1709: - Attachment: 0001-RANGER-1709-kms-test-case-write-logs-to-log-file.patch > kms test case write

[jira] [Updated] (RANGER-1709) kms test case write logs to log file

[ https://issues.apache.org/jira/browse/RANGER-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1709: - Summary: kms test case write logs to log file (was: kms test case write log to log file) > kms

[jira] [Updated] (RANGER-1710) When install ranger-1.0.0-SNAPSHOT-admin,execute ./setup.sh find [E] 007-updateBlankPolicyName.sql import failed

[ https://issues.apache.org/jira/browse/RANGER-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1710: - Summary: When install ranger-1.0.0-SNAPSHOT-admin,execute ./setup.sh find [E]

[jira] [Resolved] (RANGER-1710) When install ranger-1.0.0-SNAPSHOT-admin,execute ./setup.sh find [E] 007-updateBlankPolicyName.sql import failed

[ https://issues.apache.org/jira/browse/RANGER-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua resolved RANGER-1710. -- Resolution: Duplicate > When install ranger-1.0.0-SNAPSHOT-admin,execute ./setup.sh find [E]

[jira] [Created] (RANGER-1710) When setup cannot execute 007-updateBlankPolicyName.sql

peng.jianhua created RANGER-1710: Summary: When setup cannot execute 007-updateBlankPolicyName.sql Key: RANGER-1710 URL: https://issues.apache.org/jira/browse/RANGER-1710 Project: Ranger

[jira] [Updated] (RANGER-1710) When setup cannot execute 007-updateBlankPolicyName.sql

[ https://issues.apache.org/jira/browse/RANGER-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1710: - Description: 1.Scene： When I install ranger-1.0.0-SNAPSHOT-admin execute ./setup.sh Then

[jira] [Updated] (RANGER-1710) When install ranger-1.0.0-SNAPSHOT-admin,execute 007-updateBlankPolicyName.sql

[ https://issues.apache.org/jira/browse/RANGER-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1710: - Summary: When install ranger-1.0.0-SNAPSHOT-admin,execute 007-updateBlankPolicyName.sql (was:

[jira] [Updated] (RANGER-1710) When install setup cannot execute 007-updateBlankPolicyName.sql

[ https://issues.apache.org/jira/browse/RANGER-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1710: - Summary: When install setup cannot execute 007-updateBlankPolicyName.sql (was: When setup

[jira] [Commented] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.

[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102838#comment-16102838 ] peng.jianhua commented on RANGER-1690: -- Hi [~ankita.sinha] I verified the issue according to

[jira] [Commented] (RANGER-1690) Ranger usersync created error users. Ranger usersync got System Virtual User Group Name instead of real group name when built the unix user list.

[ https://issues.apache.org/jira/browse/RANGER-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103161#comment-16103161 ] peng.jianhua commented on RANGER-1690: -- Ok. Thanks. > Ranger usersync created error users. Ranger

[jira] [Created] (RANGER-1709) kms test case write log to log file

peng.jianhua created RANGER-1709: Summary: kms test case write log to log file Key: RANGER-1709 URL: https://issues.apache.org/jira/browse/RANGER-1709 Project: Ranger Issue Type: Bug

[jira] [Commented] (RANGER-1669) We need to support the original functionality of hive：show grant user username

[ https://issues.apache.org/jira/browse/RANGER-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098121#comment-16098121 ] peng.jianhua commented on RANGER-1669: -- Hi [~thejas], I had updated the patch according to your

[jira] [Comment Edited] (RANGER-1669) We need to support the original functionality of hive：show grant user username

[ https://issues.apache.org/jira/browse/RANGER-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098121#comment-16098121 ] peng.jianhua edited comment on RANGER-1669 at 7/24/17 9:16 AM: --- Hi

[jira] [Created] (RANGER-1677) Unable to login to Hadoop environment after opened Kerberos.

peng.jianhua created RANGER-1677: Summary: Unable to login to Hadoop environment after opened Kerberos. Key: RANGER-1677 URL: https://issues.apache.org/jira/browse/RANGER-1677 Project: Ranger

[jira] [Updated] (RANGER-1677) Unable to login to Hadoop environment after opened Kerberos.

[ https://issues.apache.org/jira/browse/RANGER-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1677: - Description: The BaseClient class used following code to login user. String encryptedPwd =

[jira] [Updated] (RANGER-1677) Unable to login to Hadoop environment after opened Kerberos.

[ https://issues.apache.org/jira/browse/RANGER-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1677: - Attachment: (was: pic1.png) > Unable to login to Hadoop environment after opened Kerberos. >

[jira] [Updated] (RANGER-1677) Unable to login to Hadoop environment after opened Kerberos.

[ https://issues.apache.org/jira/browse/RANGER-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1677: - Attachment: pic1.png > Unable to login to Hadoop environment after opened Kerberos. >

[jira] [Created] (RANGER-1678) In different places to achieve the same function, once the function is modified, it is easy to miss one of them, thus importing a new issue. We should extract the common

peng.jianhua created RANGER-1678: Summary: In different places to achieve the same function, once the function is modified, it is easy to miss one of them, thus importing a new issue. We should extract the common method for writing ranger audit

[jira] [Updated] (RANGER-1678) In different places to achieve the same function using repeat codes, new issue is perhaps generated when these functions are modified.

[ https://issues.apache.org/jira/browse/RANGER-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1678: - Attachment: (was: 0001-RANGER-1678-In-different-places-to-achieve-the-same-.patch) > In

[jira] [Updated] (RANGER-1678) In different places to achieve the same function using repeat codes, new issue is perhaps generated when these functions are modified.

[ https://issues.apache.org/jira/browse/RANGER-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1678: - Attachment: 0001-RANGER-1678-In-different-places-to-achieve-the-same-.patch > In different

[jira] [Updated] (RANGER-1678) In different places to achieve the same function using repeat codes, new issue is perhaps generated when these functions are modified.

[ https://issues.apache.org/jira/browse/RANGER-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1678: - Summary: In different places to achieve the same function using repeat codes, new issue is

[jira] [Updated] (RANGER-1540) Log is very important for big data platform. The main purpose of log analysis is that we need to know who is running the service, in which machine running service, which

[ https://issues.apache.org/jira/browse/RANGER-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1540: - Attachment: 0001-RANGER-1540-Log-is-very-important-for-big-data-platf.patch > Log is very

[jira] [Resolved] (RANGER-1723) The Ranger doesn't support solr6. In the HttpSolrClient class of solr6, the setMaxRetries function has been removed, which causes ranger to fail to compile.

[ https://issues.apache.org/jira/browse/RANGER-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua resolved RANGER-1723. -- Resolution: Fixed Fix Version/s: 1.0.0 > The Ranger doesn't support solr6. In the

[jira] [Updated] (RANGER-1725) It is incorrect to judge whether you need to create a RangerServiceDef object for a given service

[ https://issues.apache.org/jira/browse/RANGER-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1725: - Attachment: (was: 0001-RANGER-1725-It-is-incorrect-to-judge-whether-you-nee.patch) > It is

[jira] [Updated] (RANGER-1725) It is incorrect to judge whether you need to create a RangerServiceDef object for a given service

[ https://issues.apache.org/jira/browse/RANGER-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1725: - Attachment: 0001-RANGER-1725-It-is-incorrect-to-judge-whether-you-nee.patch > It is incorrect to

[jira] [Updated] (RANGER-1725) It is incorrect to judge whether you need to create a RangerServiceDef object for a given service

[ https://issues.apache.org/jira/browse/RANGER-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1725: - Description: It is incorrect to judge whether you need to create a RangerServiceDef object for

[jira] [Updated] (RANGER-1725) It is incorrect to judge whether you need to create a RangerServiceDef object for a given service

[ https://issues.apache.org/jira/browse/RANGER-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1725: - Attachment: 0001-RANGER-1725-It-is-incorrect-to-judge-whether-you-nee.patch > It is incorrect to

[jira] [Updated] (RANGER-1725) It is incorrect to judge whether you need to create a RangerServiceDef object for a given service

[ https://issues.apache.org/jira/browse/RANGER-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1725: - Description: It is incorrect to judge whether you need to create a RangerServiceDef object for

[jira] [Created] (RANGER-1725) It is incorrect to judge whether you need to create a RangerServiceDef object for a given service

peng.jianhua created RANGER-1725: Summary: It is incorrect to judge whether you need to create a RangerServiceDef object for a given service Key: RANGER-1725 URL: https://issues.apache.org/jira/browse/RANGER-1725

[jira] [Updated] (RANGER-1740) There is a exception when the ranger_credential_helper.py was executed.

[ https://issues.apache.org/jira/browse/RANGER-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1740: - Attachment: 0001-RANGER-1740-There-is-a-exception-when-the-ranger_cre.patch > There is a

[jira] [Created] (RANGER-1740) There is a exception when the ranger_credential_helper.py was executed.

peng.jianhua created RANGER-1740: Summary: There is a exception when the ranger_credential_helper.py was executed. Key: RANGER-1740 URL: https://issues.apache.org/jira/browse/RANGER-1740 Project:

[jira] [Created] (RANGER-1741) The initd ran repeatedly when ranger-usersync-services.sh was running

peng.jianhua created RANGER-1741: Summary: The initd ran repeatedly when ranger-usersync-services.sh was running Key: RANGER-1741 URL: https://issues.apache.org/jira/browse/RANGER-1741 Project:

[jira] [Updated] (RANGER-1746) The prompt message is incorrect when test hdfs connection and check 'dfs.ha.namenodes.[nameservice ID]' to be mandatory.

[ https://issues.apache.org/jira/browse/RANGER-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1746: - Attachment: incorrect prompt.PNG > The prompt message is incorrect when test hdfs connection and

[jira] [Created] (RANGER-1746) The prompt message is incorrect when test hdfs connection and check 'dfs.ha.namenodes.[nameservice ID]' to be mandatory.

peng.jianhua created RANGER-1746: Summary: The prompt message is incorrect when test hdfs connection and check 'dfs.ha.namenodes.[nameservice ID]' to be mandatory. Key: RANGER-1746 URL:

[jira] [Updated] (RANGER-1743) Comment lines have not been filtered out when the populate_global_dict function parsed install.properties in security-admin/scripts/restrict_permissions.py. Like RANGER-

[ https://issues.apache.org/jira/browse/RANGER-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1743: - Summary: Comment lines have not been filtered out when the populate_global_dict function parsed

[jira] [Created] (RANGER-1743) Comment lines have not been filtered out when the populate_global_dict function parsed install.properties in security-admin/scripts/restrict_permissions.py. Like RANGER-

peng.jianhua created RANGER-1743: Summary: Comment lines have not been filtered out when the populate_global_dict function parsed install.properties in security-admin/scripts/restrict_permissions.py. Like RANGER-1284, we should modified it.

[jira] [Updated] (RANGER-1742) Like setup.sh, the set_globals.sh should check whether the user group exists before created user group in security admin.

[ https://issues.apache.org/jira/browse/RANGER-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1742: - Attachment: 0001-RANGER-1742-Like-setup.sh-the-set_globals.sh-should-.patch > Like setup.sh, the

[jira] [Updated] (RANGER-1743) Comment lines have not been filtered out when the populate_global_dict function parsed install.properties in security-admin/scripts/restrict_permissions.py. Like RANGER-

[ https://issues.apache.org/jira/browse/RANGER-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1743: - Attachment: 0001-RANGER-1743-Comment-lines-have-not-been-filtered-out.patch > Comment lines have

[jira] [Created] (RANGER-1742) Like setup.sh, the set_globals.sh should check whether the user group exists before created user group in security admin.

peng.jianhua created RANGER-1742: Summary: Like setup.sh, the set_globals.sh should check whether the user group exists before created user group in security admin. Key: RANGER-1742 URL:

[jira] [Updated] (RANGER-1574) The XAAUDIT.DB.PASSWORD property had been deleted in RANGER-900. The related redundant code should be deleted for plugin installer.

[ https://issues.apache.org/jira/browse/RANGER-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1574: - Attachment: 0001-RANGER-1574-The-XAAUDIT.DB.PASSWORD-property-had-bee.patch > The

[jira] [Created] (RANGER-1574) The XAAUDIT.DB.PASSWORD property had been deleted in RANGER-900. The related redundant code should be deleted for plugin installer.

peng.jianhua created RANGER-1574: Summary: The XAAUDIT.DB.PASSWORD property had been deleted in RANGER-900. The related redundant code should be deleted for plugin installer. Key: RANGER-1574 URL:

[jira] [Updated] (RANGER-1574) The XAAUDIT.DB.PASSWORD property had been deleted in RANGER-900. The related redundant code should be deleted for plugin installer.

[ https://issues.apache.org/jira/browse/RANGER-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1574: - Description: The XAAUDIT.DB.PASSWORD property had been deleted in RANGER-900. The following

[jira] [Created] (RANGER-1564) The SQL_CONNECTOR_JAR properity had been deleted in RANGER-1387. The invalid code should also be deleted to keep the code consistent.

peng.jianhua created RANGER-1564: Summary: The SQL_CONNECTOR_JAR properity had been deleted in RANGER-1387. The invalid code should also be deleted to keep the code consistent. Key: RANGER-1564 URL:

[jira] [Created] (RANGER-1567) Base on RANGER-1540, we should provide the appropriate documentaion when the new version is released.

peng.jianhua created RANGER-1567: Summary: Base on RANGER-1540, we should provide the appropriate documentaion when the new version is released. Key: RANGER-1567 URL:

[jira] [Created] (RANGER-1568) Similar to RANGER-1540, the Ranger UserSync should also support the same new feature.

peng.jianhua created RANGER-1568: Summary: Similar to RANGER-1540, the Ranger UserSync should also support the same new feature. Key: RANGER-1568 URL: https://issues.apache.org/jira/browse/RANGER-1568

[jira] [Created] (RANGER-1586) There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient class.

peng.jianhua created RANGER-1586: Summary: There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient class. Key: RANGER-1586 URL: https://issues.apache.org/jira/browse/RANGER-1586

[jira] [Updated] (RANGER-1586) There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient class.

[ https://issues.apache.org/jira/browse/RANGER-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1586: - Attachment: 0001-RANGER-1586-There-is-cannot-resolve-symbol-serviceNa.patch > There is "cannot

[jira] [Updated] (RANGER-1586) There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient class.

[ https://issues.apache.org/jira/browse/RANGER-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1586: - Description: There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient class. I

[jira] [Created] (RANGER-1569) All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all Once it

peng.jianhua created RANGER-1569: Summary: All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all Once it happens. Key:

[jira] [Updated] (RANGER-1569) All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all once it

[ https://issues.apache.org/jira/browse/RANGER-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1569: - Description: Ranger is a framework to enable, monitor and manage comprehensive data security

[jira] [Updated] (RANGER-1569) All security configuration data will be loss in big data platform when the ranger was halt. It is so serious that users can not afford this serious result at all once it

[ https://issues.apache.org/jira/browse/RANGER-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1569: - Summary: All security configuration data will be loss in big data platform when the ranger was

[jira] [Updated] (RANGER-1659) Similar to RANGER-1599, Different developers use different log directories in the kms installation script. Its processing logic is chaotic. We should optimize this logic

[ https://issues.apache.org/jira/browse/RANGER-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1659: - Attachment: (was: 0001-RANGER-1659-Similar-to-RANGER-1599-Different-develop.patch) >

[jira] [Updated] (RANGER-1660) Similar to RANGER-1575, the kms should also support the same new feature.

[ https://issues.apache.org/jira/browse/RANGER-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1660: - Attachment: 0001-RANGER-1660-Similar-to-RANGER-1575-the-kms-should-al.patch > Similar to

[jira] [Resolved] (RANGER-1650) The Ranger only assigns policy to OS user. So we should filter internal users and groups when added, modified, deleted policy.

[ https://issues.apache.org/jira/browse/RANGER-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua resolved RANGER-1650. -- Resolution: Not A Bug > The Ranger only assigns policy to OS user. So we should filter

  1   2   3   4   5   >