Member since
07-09-2019
361
Posts
97
Kudos Received
56
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
968 | 08-26-2024 08:17 AM | |
1412 | 08-20-2024 08:17 PM | |
564 | 07-08-2024 04:45 AM | |
744 | 07-01-2024 05:27 AM | |
603 | 06-05-2024 06:25 AM |
12-13-2021
07:09 AM
1 Kudo
@syedshakir I see "rcmprod" user doesn't have permission to access the interpreter page To provide access to interpreter page, comment/delete below line[1] from shiro configuration url section or configure roles as mentioned in doc[2] [1]: /api/interpreter/** = authc, roles[admin] [2]: https://zeppelin.apache.org/docs/0.6.2/security/shiroauthentication.html#active-directory
... View more
12-01-2021
08:51 PM
If you are using the Postgres DB then use the below query to get table information : 1. log in to DB server and execute the below query : ./psql -d hive -c "SELECT \"NAME\", \"TBL_NAME\" FROM \"DBS\" as a, \"TBLS\" as b where a.\"DB_ID\"=b.\"DB_ID\";" > /tmp/tables1.txt
> awk '{print $1" " $3}' tables1.txt >> tables.txt
> cat /tmp/tables1.txt | wc -l
... View more
11-10-2021
09:53 PM
Hello @yacine_ Thanks for sharing the Solution along with the Root Cause as well. We shall mark the Post as Solved for now to ensure fellow Community Users can use the Solution as well. Regards, Smarak
... View more
10-21-2021
01:40 PM
Hi @PrernaU , It seems like the logged in user does not have permission to access the interpreter page. The authorization is dependent on how you have configured your shiro authentication. If you have integrated your AD with zeppelin the make sure the role mapping has done correctly and you have the correct user/group defined in the shiro roles section.
... View more
09-22-2021
06:52 AM
@wbivp I created a community article long ago that details the Ranger based "NiFi Resource Identifier" policy strings you would use in Ranger to provide various levels of authorization within NiFi. https://community.cloudera.com/t5/Community-Articles/NiFi-Ranger-based-policy-descriptions/ta-p/246586 For example, it you want to grant access so that users can access and create components within a PG: /process-groups/<uuid of PG> . Grant Read and Write for your "group" and/or "user" to allow them to view configurations and added components (processors, controller services, child PGs, etc...) within this PG /data/process-groups/<uuid of PG> Granting Read and Write for your "group" and/or "user" to allow user to view and delete content (flowfiles) queued within connection within this PG. Keep in mind that child PGs will inherit the access granted to the parent PG unless explicit policies have been set on the child PG. Hope this helps, Matt
... View more
09-07-2021
07:48 AM
@HeathG I'm happy to see you resolved your issue. Please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
08-31-2021
10:55 PM
1 Kudo
@KPG1 Ranger audits store in both HDFS and Solr. HDFS is used for long term , Solr will be used for short term storage. By using Solr you have data indexed and you can view it quickly from Ranger UI. Deleting older ranger audit from hdfs will not cause any issues to the service
... View more
08-30-2021
08:59 AM
@ajck, have you found a solution for your issue? If you have, can you please post the appropriate solution here? If you are still experiencing the issue, can you provide the information @Scharan has requested?
... View more
08-17-2021
05:16 AM
Remove smartsense package from server and retry yum remove smartsense-hst
rm -rf /var/log/smartsense/
... View more
08-13-2021
09:44 PM
@Nil_kharat Ticket lifetime is set in kerberos configuration file krb5.conf in MIT kerberos, You can check the lifetime of the ticket using # klist command after doing kinit You can still specify the lifetime of the ticket using -l option as shown below # kinit -l 30m -kt <Keytab> <principal>
Example:
kinit -l 30m -kt sai.keytab sai@SUPPORTLAB.CLOUDERA.COM
... View more