Hue 3.10.0 + HiveServer2 with hive.server2.thrift.sasl.qop=auth-conf sometimes(or always on certain conditions) reports a SASL error shown below: Error in sasl_decode (-1) SASL(-1): generic failure: Unable to find a callback: 32775 (code THRIFTTRANSPORT): TTransportException('Error in sasl_decode (-1) SASL(-1): generic failure: Unable to find a callback: 32775',) I can see this message when executing, for example, "select * from db.table limit 12;", but cannot see when executing "select * from db.table limit 11;"... These queries are same only except for "limit" clause. I searched with that error message, so I found this post: https://groups.google.com/a/cloudera.org/forum/#!topic/hue-user/0LfySJBERsc A poster said "Seems hue doesn't play nice with hive.server2.thrift.sasl.qop set to auth-conf. Works OK with only auth though." in this post. Is that also true on Hue 3.10.0? Is it impossible to use sasl.qop=auth-conf on Hue 3.10.0? ... View more

I found that Ambari creates Hive View on its restart automatically. But I want to block that. How do I block Ambari from creating Hive View on its restart? ... View more

A host that JournalNode is assigned went down by hardware trouble. So I want to move that JournalNode to another host. However, I can't find the way how to move or add JournalNode by Ambari. Is it impossible to move or add JournalNode by Ambari? ... View more

I found it may be possible to set a session timeout of Ranger Admin WebUI by modifying <session-timeout> parameter in web.xml (usually placed in /usr/hdp/${version}/ranger-admin/ews/webapps/WEB-INF), however, this parameter cannot be set via Ambari WebUI. Is it the best way to modify web.xml on Ranger Admin host? If not, what is the best way for it? ... View more

I modified(tampered) a local policy file written by Ranger HDFS Plugin to test against illegal or malicious operation, but authorization rules are not changed. For example: 1. user "ohide" cannot read /user/ohide 2. admit user "ohide" to read /user/ohide by Ranger 3. confirm user "ohide" can read /user/ohide 4. delete an entry added by step 2 from a local policy cache file in NameNode host (where Ranger HDFS Plugin running) 5. try to read /user/ohide by user "ohide" and succeeded. This behavior is appropriate I think, but I do not know and want to know how to avoid not to read tampered policy cache file. Does anyone know the answer of my question? ... View more