It's a bit confusing and we should fix the docs.  You need the Mysql 5.1 libraries availble, but you can have Mysql 5.7 installed.  There is a compat rpm you can install instead.  Search for something like this in Yum or your rpms:   mysql-community-libs-compat-5.7.16-1.el7.x86_64.rpm ... View more

Hue sends queries to HiveServer2, so you would want to implement it in the CM configuration for HS2, which is this safety valve in the Hive service: HiveServer2 Advanced Configuration Snippet (Safety Valve) for hive-site.xml ... View more

Great, just wanted to make sure we took care of any problems you might have been running into:-). Did that answer your question? ... View more

Jira filed:-) https://issues.cloudera.org/browse/HUE-2749 Right now Hue requires both Impala and HS2 to be configured for Ldap, so ldap_username and ldap_password are global. There is also a feature request out there to make those specific for Impala and HS2 so that would be less of an issue in the future. ... View more

Ahhh, that is why:-). Those properties: [desktop] ldap_username ldap_password Tell Hue to use ldap when authenticating against Impala and HS2. So if you're not using ldap for Impala and HS2, then you can remove those and you don't need ldap for Impala. ... View more

Oh, sorry, meant which ldap properties did you have set for Hue? Mainly, did you have: [desktop] ldap_username= ldap_password= ... View more

Just curious, what ldap properties did you have set for Hue? Hue being configured for Ldap should not force Impala to require Ldap. ... View more

There is an issue with hive where HS2 has problems renewing tokens after the renewal period and it throws the error you are seeing.  If you restart the Hive service, Hue will probably start working again for a day or two.  You can alleviate this by adding the following to the HMS and HS2 safety valves:   <property> <name>hive.cluster.delegation.key.update-interval</name> <value>31536000000</value> </property> <property> <name>hive.cluster.delegation.token.renew-interval</name> <value>31536000000</value> </property> <property> <name>hive.cluster.delegation.token.max-lifetime</name> <value>31536000000</value> </property>   This will set the token renewal to 1 year, so this will only happen once a year.   Hope this helps. ... View more

With a kerberized cluster, your connect string needs to include the HS2 server principal, so:   jdbc:hive2://cdh53-1.qa.test.com:10000/default;principal=hive/cdh53-1.qa.test.com@TEST.COM   replace "cdh53-1.qa.test.com" with your fully qualified host and domain name.  Replace TEST.COM with the correct REALM.  Any time kerberos is in place, you must use the hostname and fully qualified domain name instead of localhost or hostname as kerberos checks depend on the FQDN.  Same is true of the Sentry server in your safety valve configuration, use the FQDN instead of localhost. ... View more

In your shell action, go to "Files" and click "Add path" and then browse to your shell script in HDFS.  Then save and run it again and see if that helps.  If it does not help, try removing the "#!/...." line at the top of the script and see if that helps. ... View more

This right here works:   <workflow-app name="shell-impala-invalidate-wf" xmlns="uri:oozie:workflow:0.4"> <start to="shell-impala-invalidate"/> <action name="shell-impala-invalidate"> <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-impala-invalidate.sh</exec> <file>shell-impala-invalidate.sh#shell-impala-invalidate.sh</file> <file>shell-impala-invalidate.sql#shell-impala-invalidate.sql</file> <file>cconner.keytab#cconner.keytab</file> </shell> <ok to="end"/> <error to="kill"/> </action> <kill name="kill"> <message>Action failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/> </workflow-app>   Script: #!/bin/bash LOG=/tmp/shell-impala-invalidate-$USER.log ls -alrt > $LOG export PYTHON_EGG_CACHE=./myeggs /usr/bin/kinit -kt cconner.keytab -V cconner /usr/bin/klist -e >> $LOG impala-shell -f shell-impala-invalidate.sql   NOTE: the <file> tag puts that file on the local file system where the impala-shell is going to run, so the file is indeed local for the -f flag and it goes in "PWD/<whatever is after #>".  For example:   <file>test.sql#/test1/test.sql</file>   Then test.sql will be found in:   PWD/test1/test.sql   And:   <file>test.sql#test.sql</file>   Then test.sql will be found in:   PWD/test.sql   And the shell script and the keytab are also in "PWD" because of the file tags.  I would do the following in your shell script to get some more insight:     #!/bin/bash LOG=/tmp/shell-impala-invalidate-$USER.log ls -alrtR > $LOG  #This will show you all the files in the directory and their relative paths export PYTHON_EGG_CACHE=./myeggs /usr/bin/kinit -kt cconner.keytab -V cconner /usr/bin/klist -e >> $LOG hadoop fs -put $LOG /tmp  #put the log file in HDFS to find it easily impala-shell -f shell-impala-invalidate.sql     NOTICE the "ls -lartR" and the "hadoop fs" command, this way you can easily grab the log file from HDFS and see what files are actually there.     ... View more

The method you did was correct and should have worked.  Did you try a command like:   impala-shell -f ./file.sql     ... View more

Glad to hear that worked!  Hue doesn't currently support Framed Thrift to Hbase.  It's on the roadmap, but not sure when. ... View more

Go to the http://<hueserver>:<port>/desktop/dump_config and in the "Configuration Sections and Variables" section go to hbase and confirm that "hbase_clusters" points to the correct thrift server. If that's not correct, confirm in the Hue service-wide config that you have the Hbase service selected. If that is correct, then go to the Hbase service configuration and check to see if this property is enabled, " Enable HBase Thrift Server Framed Transport".  If it is, try unchecking it and restarting the Hbase thrift server and see if that works. ... View more

Glad to hear it!! ... View more

Glad it worked! ... View more

That's right, you'll have to put the following in your Hue Service->Configuration->Hue Server->Advanced-> Hue Server Configuration Safety Valve for hue_safety_valve_server.ini:     [hadoop] [[mapred_clusters]] [[[default]]] jobtracker_host=cdh45-2.qa.test.com thrift_port=9290 jobtracker_port=8021 submit_to=true hadoop_mapred_home={{HADOOP_MR1_HOME}} hadoop_bin={{HADOOP_BIN}} hadoop_conf_dir={{HADOOP_CONF_DIR}} security_enabled=true logical_name=logicaljt [[[jtha]]] jobtracker_host=cdh45-1.qa.test.com thrift_port=9290 jobtracker_port=8021 submit_to=true hadoop_mapred_home={{HADOOP_MR1_HOME}} hadoop_bin={{HADOOP_BIN}} hadoop_conf_dir={{HADOOP_CONF_DIR}} security_enabled=true logical_name=logicaljt     Leaving off "secuirty_enabled=true" if you're not using kerberos. ... View more

This is also fixed in CDH 4.6 and there is a Patched version of CDH 4.5 that resolves this as well.  You can open a support ticket to get the patched version of 4.5 if you are running CDH 4.5.  You would have to add a new parameters "logical_name", for example:   [hadoop] [[mapred_clusters]] [[[default]]] jobtracker_host=cdh45-2.qa.test.com thrift_port=9290 jobtracker_port=8021 submit_to=true hadoop_mapred_home={{HADOOP_MR1_HOME}} hadoop_bin={{HADOOP_BIN}} hadoop_conf_dir={{HADOOP_CONF_DIR}} security_enabled=true logical_name=logicaljt [[[jtha]]] jobtracker_host=cdh45-1.qa.test.com thrift_port=9290 jobtracker_port=8021 submit_to=true hadoop_mapred_home={{HADOOP_MR1_HOME}} hadoop_bin={{HADOOP_BIN}} hadoop_conf_dir={{HADOOP_CONF_DIR}} security_enabled=true logical_name=logicaljt   Hope this helps. ... View more

Hey Andrew,   Can you try adding "oozie.libpath=/application/lib" to your job.properties and see if that helps?   Thanks Chris ... View more

Hey Andrew,   Where are you storing the jars that you need in the distributed cache?  Are they in the "${oozie.wf.application.path}/lib" or another location in HDFS?   Thanks Chris ... View more