Google Git
Sign in
apache / ranger / 199a8157eea9a2864cffc5ccdbe99fc7bd634bb2
commit199a8157eea9a2864cffc5ccdbe99fc7bd634bb2[log] [tgz]
authorAbhishek Kumar <abhishekkumar100031@gmail.com>Thu Dec 12 09:01:34 2024 -0800
committerGitHub <noreply@github.com>Thu Dec 12 09:01:34 2024 -0800
treeda49f9ca905f6f2a61c2ae7dd7175b2ca67475c7
parent47670e679f7d4125da3f30a2e8a66d715582cc16 [diff]
RANGER-5043: checkstyle compliance updates - plugin-nestedstructure module (#449)
18 files changed
tree: da49f9ca905f6f2a61c2ae7dd7175b2ca67475c7
  1. .github/
  2. agents-audit/
  3. agents-common/
  4. agents-cred/
  5. agents-installer/
  6. credentialbuilder/
  7. dev-support/
  8. distro/
  9. docs/
  10. embeddedwebserver/
  11. hbase-agent/
  12. hdfs-agent/
  13. hive-agent/
  14. intg/
  15. jisql/
  16. kms/
  17. knox-agent/
  18. migration-util/
  19. plugin-atlas/
  20. plugin-elasticsearch/
  21. plugin-kafka/
  22. plugin-kms/
  23. plugin-kudu/
  24. plugin-kylin/
  25. plugin-nestedstructure/
  26. plugin-nifi/
  27. plugin-nifi-registry/
  28. plugin-ozone/
  29. plugin-presto/
  30. plugin-schema-registry/
  31. plugin-solr/
  32. plugin-sqoop/
  33. plugin-trino/
  34. plugin-yarn/
  35. ranger-atlas-plugin-shim/
  36. ranger-authn/
  37. ranger-common-ha/
  38. ranger-elasticsearch-plugin-shim/
  39. ranger-examples/
  40. ranger-hbase-plugin-shim/
  41. ranger-hdfs-plugin-shim/
  42. ranger-hive-plugin-shim/
  43. ranger-kafka-plugin-shim/
  44. ranger-kms-plugin-shim/
  45. ranger-knox-plugin-shim/
  46. ranger-kylin-plugin-shim/
  47. ranger-metrics/
  48. ranger-ozone-plugin-shim/
  49. ranger-plugin-classloader/
  50. ranger-presto-plugin-shim/
  51. ranger-solr-plugin-shim/
  52. ranger-sqoop-plugin-shim/
  53. ranger-storm-plugin-shim/
  54. ranger-tools/
  55. ranger-util/
  56. ranger-yarn-plugin-shim/
  57. security-admin/
  58. storm-agent/
  59. tagsync/
  60. ugsync/
  61. ugsync-util/
  62. unixauthclient/
  63. unixauthnative/
  64. unixauthpam/
  65. unixauthservice/
  66. .asf.yaml
  67. .gitattributes
  68. .gitignore
  69. .travis.yml
  70. build_ranger_using_docker.sh
  71. DISCLAIMER.txt
  72. enunciate.xml
  73. LICENSE.txt
  74. NOTICE.txt
  75. pom.xml
  76. ranger_in_docker
  77. README.md
  78. release-build.xml
README.md

Apache Ranger

License PyPI Downloads Documentation Wiki

NOTE

Apache Ranger allows contributions via pull requests (PRs) on GitHub.
Alternatively, use this to submit changes for review using the Review Board. Also create a ranger jira to go along with the review and mention it in the review board review.

Building Ranger in Docker (Sandbox Install)

Ranger is built using Apache Maven. To run Ranger:

  1. Check out the code from GIT repository

  2. Ensure that docker & docker-compose is installed and running on your system.

  3. Ensure that JDK 1.8+ is installed on your system.

  4. Ensure that Apache Maven is installed on your system.

  5. Run the following command to build & run Ranger from Docker

    ./ranger_in_docker up

  6. After successful completion of the above command, you should be able to view Ranger Admin Console by using URL:

     http://<hostname-of-system>:6080/

 UserName: admin
 Password: rangerR0cks!

Regular Build Process

  1. Check out the code from GIT repository

  2. On the root folder, please execute the following Maven command:

    mvn clean compile package install

    mvn eclipse:eclipse

    Ranger Admin UI tests depend on PhantomJS. If the build fails with npm or Karma errors you can either:

    • install PhantomJS dependencies for your platform (bzip2 and fontconfig)
    • skip JavaScript test execution: mvn -DskipJSTests ...

  3. After the above build command execution, you should see the following TAR files in the target folder:

    ranger-<version>-admin.tar.gz
ranger-<version>-atlas-plugin.tar.gz
ranger-<version>-hbase-plugin.tar.gz
ranger-<version>-hdfs-plugin.tar.gz
ranger-<version>-hive-plugin.tar.gz
ranger-<version>-kafka-plugin.tar.gz
ranger-<version>-kms.tar.gz
ranger-<version>-knox-plugin.tar.gz
ranger-<version>-migration-util.tar.gz
ranger-<version>-ranger-tools.tar.gz
ranger-<version>-solr-plugin.tar.gz
ranger-<version>-sqoop-plugin.tar.gz
ranger-<version>-src.tar.gz
ranger-<version>-storm-plugin.tar.gz
ranger-<version>-tagsync.tar.gz
ranger-<version>-usersync.tar.gz
ranger-<version>-yarn-plugin.tar.gz
ranger-<version>-kylin-plugin.tar.gz
ranger-<version>-elasticsearch-plugin.tar.gz

Importing Apache Ranger Project into Eclipse

  1. Create an Eclipse workspace called ‘ranger’

  2. Import maven project from the root directory where ranger source code is downloaded (and build)

Deployment Process

Installation Host Information

  1. Ranger Admin Tool Component (ranger--admin.tar.gz) should be installed on a host where Policy Admin Tool web application runs on port 6080 (default).
  2. Ranger User Synchronization Component (ranger--usersync.tar.gz) should be installed on a host to synchronize the external user/group information into Ranger database via Ranger Admin Tool.
  3. Ranger Component plugin should be installed on the component boxes:
    • HDFS Plugin needs to be installed on Name Node hosts.
    • Hive Plugin needs to be installed on HiveServer2 hosts.
    • HBase Plugin needs to be installed on both Master and Regional Server nodes.
    • Knox Plugin needs to be installed on Knox gateway host.
    • Storm Plugin needs to be installed on Storm hosts.
    • Kafka/Solr Plugin needs to be installed on their respective component hosts.
    • YARN plugin needs to be installed on YARN Resource Manager hosts.
    • Sqoop plugin needs to be installed on Sqoop2 hosts.
    • Kylin plugin needs to be installed on Kylin hosts.
    • Elasticsearch plugin needs to be installed on Elasticsearch hosts.

Installation Process

  1. Download the tar.gz file into a temporary folder in the box where it needs to be installed.

  2. Expand the tar.gz file into /usr/lib/ranger/ folder

  3. Go to the component name under the expanded folder (e.g. /usr/lib/ranger/ranger--admin/)

  4. Modify the install.properties file with appropriate variables

    • If the module has setup.sh, execute ./setup.sh
    • If the install.sh file does not exists, execute ./enable--plugin.sh