Unfortunately there is no way to provide super user access to an entire group today.  It must be done one user at a time.  There is a feature request to add this in a future release.  You could do it programatically to make it a little easier, see the section "How to make a certain user a Hue admin"   http://gethue.com/password-management-in-hue/   You could create a list of users and iterate through them in hue shell.  Make sure to set HUE_CONF_DIR=/var/cloudera-scm-agent/process/id-hue-HUE_SERVER where id is most recent.  ON CDH 5.5 and above you also have to set:   export HUE_IGNORE_PASSWORD_SCRIPT_ERRORS=1 export HUE_DATABASE_PASSWORD=huedatabasepassword   Hope this helps.   ... View more

Hey, The way it works is the Hue launcher job acts like the Hive CLI and then spawns the Hive MR job. So you will never see an actual instance of hive spin up, you'll just see a launcher MR job and then a hive MR job. Are you having an issue or just curious? ... View more

Did you include:   HADOOP_OPTS="-Djava.security.auth.login.config=/path/to/jaas.conf"   Before your "hadoop jar" command?  IE:     HADOOP_OPTS="-Djava.security.auth.login.config=/path/to/jaas.conf" hadoop jar /opt/cloudera/parcels/CDH/lib/solr/contrib/mr/search-mr-*-job.jar org.apache.solr.hadoop.MapReduceIndexerTool -D 'mapred.child.java.opts=-Xmx2048m' -Djava.security.auth.login.config=/home/user/clouderaSearch/test_collection/jaas.conf --log4j /opt/cloudera/parcels/CDH/share/doc/search-1.0.0+cdh5.4.0+0/examples/solr-nrt/log4j.properties --morphline-file /home/user/clouderaSearch/test_collection/test_morphline.conf --output-dir hdfs://nameservice1:8020/data/test/output_solr --verbose --go-live --zk-host zookeeper_host:2181/solr --collection test_collection hdfs://nameservice1:8020/data/test/incoming   Notice how "HADOOP_OPTS" and "hadoop jar" are on the same line, that is how they need to be. ... View more

You can do the following:   1.  Spawn the Hue shell:   export HUE_CONF_DIR="/var/run/cloudera-scm-agent/process/`ls -alrt /var/run/cloudera-scm-agent/process | grep HUE | tail -1 | awk '{print $9}'`" cd /opt/cloudera/parcels/CDH/lib/hue (or /usr/lib/hue if using packages) ./build/env/bin/hue shell   2.  Paste the following python in the shell replacing <username> with the user you want to become superuser:   from django.contrib.auth.models import User a = User.objects.get(username='<username>') a.is_staff = True a.is_superuser = True a.save() ... View more

There are 2 options here: 1. If using CM, put a Hive gateway on every NodeManager/TaskTracker in the cluster, if not using CM, put the hive-site.xml in /etc/hive/conf on every NodeManager/TaskTracker. 2. Add "export HIVE_CONF_DIR=`pwd`" to the top of your shell script and then sqoop shoudl check the local directory for the hive-site.xml. ... View more

Hey,   To share your workflows in Hue, do the following:   1.  Go to your home page in Hue by clicking on the little house icon in the upper left to the right of "HUE". 2.  Select the Project that contains the workflow, probably "default". 3.  Here you can share anything with others, workflows, queries etc.  Find what you want to share and click on the "Sharing" icon on the far right of the page, looks like a few people standing together.  4.  Then enter the user/group you want to share with and the perms you want to give them.     ... View more

Hey,   You can't have a kill action send an email.  However, you can have your other actions change their kill to be an email action that sends the email and then the email action goes to a kill.  Like:   <workflow-app name="shell-wf" xmlns="uri:oozie:workflow:0.4"> <start to="shell"/> <action name="shell"> <shell xmlns="uri:oozie:shell-action:0.1"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <configuration> <property> <name>mapred.job.queue.name</name> <value>${queueName}</value> </property> </configuration> <exec>shell.sh</exec> <file>shell.sh#shell.sh</file> </shell> <ok to="end"/> <error to="kill-email"/> </action> <action name="kill-email"> <email xmlns="uri:oozie:email-action:0.1"> <to>cconner@test.com</to> <cc>other-cconner@test.com</cc> <subject>WF ${wf:id()} failed</subject> <body>Shell action failed.</body> </email> <ok to="kill"/> <error to="kill"/> </action> <kill name="kill"> <message>Action failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/> </workflow-app> ... View more