Hello @jludac ,    I understand you are not able to get an "archive" build with your Cloudera login credentials.    You will need different credentials(paywall credentials) to download the build.  Paywall credentials are required to access the same.    Can you please reach contact the Cloudera support team to progress ahead?    Thanks,   ... View more

Hello @Pravin93    1) Within Cloudera Navigator, you can apply metadata and tagging via the Navigator UI or the Navigator API.  Please see the below links for each: https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cn_iu_metadata_modify.html#xd_583c10... https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cn_nav_hive-hdfs_api.html#tag_hive_h...   2) Apache Sentry provides only Role-Based Access Control (RBAC) policies.  Creating access policies based on metadata and tags is more commonly referred to as Attribute-Based Access Control (ABAC).  Navigator+Sentry in CDH6.3 does not provide ABAC functionality.  You will need Atlas and Ranger available in CDP which can support both RBAC and ABAC policies.  Please see an overview of ABAC in this Cloudera Youtube video on ABAC.   Thanks, Azhar ... View more

Hello @Former Member    Good Day.    Were you able to access the Cloudera Manager Ui earlier?   - Do you have access to the environment? You can check the access you have on the left bottom of the environment page (it will display your username).  You can click on your username and check the access you have to the environment.    - You can grant yourself the environment access as per your role.  If you want complete access you can opt yourself for the "Environment admin" access role.  Once you update the same please synchronize the user (you can see it top right tab of your screen).   - Logout from the cdp console and try to access the UI again.    Please let us know If you are able to access the same.    Thanks, Azhar ... View more

Hello @IAJ,    Good Day.    From the error in the community post I see " Proposed configuration is not inheritable by the flow controller because of flow differences: Found difference in Flows: Local Fingerprint"    - I see the flow.xml.gz is not in sync with the coordinator (nifi node). - You can follow the below steps to get the node connected to the cluster.        1) SSH to the nifi node which is disconnected from the nifi cluster.        2) Take a backup of the existing flow.xml.gz and move it to a different location.         3) Remove the flow.xml.gz after taking the backup (make sure you note the permission and ownership               of the flow.xml.gz )         4) SSH into the coordinator nifi node, you can see the coordinator node on nifi cluster, where you see all the  nodes are disconnected/disconnected        5) SCP the flow.xml.gz from the coordinator node to the disconnected nifi node (in your home folder).        6) Now copy the flow.xml.gz to the exact location from where you have removed the flow.xml.gz                       (step3) , once you copy it to the original location make sure the permissions and ownership are                      updated properly.        7) Once the steps are followed try to restart the node from .from backend uisng ./nifi.sh start (you need to find the location where are those scripts in your cluster.  Don't connect the node from nifi UI.   Another way is to take backup of flow.xml.gz on the disconnected node and remove the flow.xml.gz from the location and start the nifi service.  make sure there is no defunct/zoombie process already running for nifi on the disconnected node.   === Reason for disconnection and reconnection : - Can you please confirm If there are multiple processors that are in disabled states? And How many templates are there in your nifi registry?   ... View more

Hello @ChandravadanD    I see you have registered for the free trial and have not received the access details.    You will need to reach out to the Cloudera Sales team to check this.  ... View more

Hello @SimonBergerard    Can you take a look at https://my.cloudera.com/knowledge/ERROR-quot-MountVolume-SetUp-failed-for-volume-quot?id=327405 seems your issue is related to the same article?  If your issue gets resolved following the article you can accept this as the solution on this page.  ... View more