Ranger installation was successful and the Ranger admin portal should be accessible at http://localhost:6080/ with the credentials "admin/rangerR0cks!".

However, we are still unable to connect to Ranger's admin panel. We've checked if the Ranger admin service is running by using the command "systemctl status ranger-admin" in the terminal, and we realised it wasn't running. We then tried starting it with the command "systemctl start ranger-admin", but still no success. We tried reinstalling it but still no success.

Once this is sorted, we should be able to deploy access control as shown in our pipeline diagram.

.

Apache Atlas Web UI runs, but we are unable to connect the Kafka-Hook to it or even install other hooks required for it to run.

We attempted to solve the problem by running the mvn clean install -DskipTests command in the root directory of our Kafka Bridge project folder, where the pom.xml file is located. In this case, we ran it in the kafka-bridge directory, as that's where the pom.xml file is located, but we got the following error:

central-https: https://repo.maven.apache.org/maven2/com/puppycrawl/tools/checkstyle/5.5/checkstyle-5.5.jar (638 kB at 85 kB/s)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  42:53 min
[INFO] Finished at: 2023-04-12T11:50:49+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check (checkstyle-check) on project kafka-bridge: Execution checkstyle-check of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1 or one of its dependencies could not be resolved: Could not find artifact org.apache.atlas:atlas-buildtools:jar:1.0 in central-https (https://repo.maven.apache.org/maven2) -> [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.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

The error message suggested that Maven was not able to find the artifact "org.apache.atlas:atlas-buildtools:jar:1.0". So one possible solution was to add the repository where this artifact is hosted to our Maven settings.xml file. Here are the steps you followed without success:

1. Open our settings.xml file located in ~/.m2/settings.xml with our text editor.
2. Add the following code snippet inside the tag:

<repository>
    <id>atlas-repository</id>
    <name>Apache Atlas Repository</name>
    <url>https://repository.apache.org/content/repositories/releases/</url>
</repository>

3. Save the settings.xml file and re-run the mvn clean install -DskipTestscommand.

The above addition failed, then we tried one last option, which entailed adding the following repository to our pom.xml file:

<repositories>
  <repository>
    <id>atlas-repository</id>
    <name>Apache Atlas Repository</name>
    <url>https://repository.apache.org/content/groups/public/</url>
  </repository>
</repositories>

This addition still did not work. For this reason, we couldn't successfully install the Kafka-Hook required for Apache Atlas to run and pull Kafka topics. This hindered our ability to run Atlas for Data Discovery, Data Lineage and Data Governance in general.

A solution will be most appreciated!