About KuldeepK

KuldeepK · ‎12-17-2015

Hey Guys, Is it possible to create hive database name in UPPERCASE ? hive> create database KULDEEP; hive> show databases; OK default kuldeep test Time taken: 0.464 seconds, Fetched: 3 row(s)

KuldeepK · ‎12-17-2015

I do have access to hdfs user and yes we can change the ownership using sudo -u hdfs hadoop fs -chown <some-user> /user/oozie/test1 I just wanted to ensure that if this is expected behavior that even after granting rwx via Ranger authorization we cannot change the ownership.

KuldeepK · ‎12-17-2015

@bdurai - nopes I have just configured ranger policy and given rwx access to admin user for /user/oozie (recursively)

KuldeepK · ‎12-17-2015

@Neeraj Sabharwal - its owned by admin only [root@hdpambari yarn]# hadoop fs -ls /user/oozie/test1 -rw-r--r-- 3 admin hadoop 0 2015-12-09 21:47 /user/oozie/test1 [root@hdpambari yarn]#

KuldeepK · ‎12-17-2015

@mkhandekar

KuldeepK · ‎12-17-2015

@Benjamin Leonhardi - Yes I can do dfs -ls /user/oozie, I can read each and every file, I can write into it. You are correct! its same as Unix. @Jonas Straub - Thank you for the link. I think only superuser can change the ownership ( current owner also cannot change it) Unix: -rwxrwxrwx 1 kkulkarni staff 39441 Dec 17 08:17 test KKs-Mac:~ kkulkarni$ KKs-Mac:~ kkulkarni$ chown root test chown: test: Operation not permitted KKs-Mac:~ kkulkarni$ sudo chown root test KKs-Mac:~ kkulkarni$ ls -lrt test -rwxrwxrwx 1 root staff 39441 Dec 17 08:17 test KKs-Mac:~ kkulkarni$ Same is the case for hdfs.

KuldeepK · ‎12-16-2015

@Arti Wadhwani

KuldeepK · ‎12-16-2015

I have configured once policy for hdfs via ranger. below are the details: 1. Policy configured for user admin 2. User admin can rwx into /user/oozie 3. Point number 2 tested successfully 4. When I went to change ownership of /user/oozie to admin by user admin then it fails with below error [admin@hdpambari ~]$ hdfs dfs -chown root /user/oozie/test1 chown: changing ownership of '/user/oozie/test1': Non-super user cannot change owner I know that logically this is correct as user "admin" has rwx access to /user/oozie so no need to change the ownership. Is my understanding correct ? is there any documentation that points to this ?

KuldeepK · ‎12-15-2015

@Sam Mingolelli - it looks like there is configuration error in capacity scheduler, could you please attach your capacity-scheduler.xml here ? ( default location - /etc/hadoop/conf/capacity-scheduler.xml) Default working configuration attached. - default-capacity-scheduler.txt

KuldeepK · ‎12-12-2015

@rmaruthiyodan, @Jonas Straub Agreed! We might need to run hive metatool to update existing nameservice URI.

Online	Offline
Last Visited	‎04-07-2022 05:11 PM

Member Since	‎04-03-2019 04:03 PM
Last Visited	‎04-07-2022 05:11 PM
Posts	962
Kudos received	1733

Cloudera Community

Re: oozie shell action

Re: Oozie Service Check fails after upgrading to ...

Re: oozie - mr container fails to start on rhel6 n...

Re: Not able to run docker container on yarn even ...

Re: Oozie Pig action doesn't appear in Tez UI

Uppercase hive DB name

Re: Ranger authorization for HDFS - Unable to chan...

Re: Ranger authorization for HDFS - Unable to chan...

Re: Ranger authorization for HDFS - Unable to chan...

Re: Ranger authorization for HDFS - Unable to chan...

Re: Ranger authorization for HDFS - Unable to chan...

Re: Ranger authorization for HDFS - Unable to chan...

Ranger authorization for HDFS - Unable to change o...

Re: ResourceManager cannot start

Re: Renaming NameNode HA logical Name "dfs.nameser...