Hi, Based on the error: Unable to obtain Principal Name for authentication This can happen when the JCE jars are not up to date on the client machine and not able to use the encryption key provided by Kerberos KDC. The solution is to download the latest/appropriate jce jars and place them in directory $JAVA_HOME/jre/lib/security. The files are: US_export_policy.jar local_policy.jar Please give it a try and see if it can be helpful. ... View more

Hi,   On top of what Gomath has suggested, I also have another idea:   1. assuming that your current data on HDFS is /user/hive/wareshouse/dbname/tablename/columnA=1 /user/hive/wareshouse/dbname/tablename/columnA=2 /user/hive/wareshouse/dbname/tablename/columnA=3 /user/hive/wareshouse/dbname/tablename/columnA=4 ....   and you want it to become:   /user/hive/wareshouse/dbname/tablename/columnA=1/columnB=1 /user/hive/wareshouse/dbname/tablename/columnA=2/columnB=1 /user/hive/wareshouse/dbname/tablename/columnA=3//columnB=1 /user/hive/wareshouse/dbname/tablename/columnA=4/columnB=1 ...   2. create a new table that has the same columns, but with extra partition columnB, assuming that you will create under HDFS in /user/hive/wareshouse/dbname/new_tablename   3. you can create a new directory with below structure:   /user/hive/wareshouse/dbname/new_tablename/columnA=1 /user/hive/wareshouse/dbname/new_tablename/columnA=2 /user/hive/wareshouse/dbname/new_tablename/columnA=3 /user/hive/wareshouse/dbname/new_tablename/columnA=4 ...   4. create the top level partition directories for the new table   hadoop fs -mkdir /user/hive/wareshouse/dbname/new_tablename/columnA=1 hadoop fs -mkdir /user/hive/wareshouse/dbname/new_tablename/columnA=2 hadoop fs -mkdir /user/hive/wareshouse/dbname/new_tablename/columnA=3 hadoop fs -mkdir /user/hive/wareshouse/dbname/new_tablename/columnA=4 5. and then MOVE data from old table into new table's partition:   hadoop fs -mv /user/hive/wareshouse/dbname/tablename/columnA=1 /user/hive/wareshouse/dbname/new_tablename/columnA=1/columnB=1 hadoop fs -mv /user/hive/wareshouse/dbname/tablename/columnA=2 /user/hive/wareshouse/dbname/new_tablename/columnA=2/columnB=1 hadoop fs -mv /user/hive/wareshouse/dbname/tablename/columnA=3 /user/hive/wareshouse/dbname/new_tablename/columnA=3/columnB=1 hadoop fs -mv /user/hive/wareshouse/dbname/tablename/columnA=4 /user/hive/wareshouse/dbname/new_tablename/columnA=4/columnB=1 ....   What's the value for columnB you will decide, since it is a new partition.   6. get back to hive and then run below command:   MSCK REPAIR TABLE dbname.new_tablename;   This will help to recover all the missing partitions   7. Run:   SELECT * FROM dbname.new_tablename    to confirm if data is correct.   This way, you do not need to duplicate any data on HDFS.   Hope above helps. ... View more

This could be just networking issue. Was your HMS working at the time? How often this happens? Is it intermittent or always? Or only when running certain queries? Some context on the error might help. Cheers ... View more

Hi, I have tested, it seems like if you make the variable in HQL and the variable in the parameters section to be the same name, it will work. So update the parameter to be "zip=${zip}", rather than "zip={$zip_code}", then Hue will ask for the value of zip, and it will pass along the value correctly. Cheers ... View more

Hi, I assume that you work on the managed table instead of external table? This could be because of lack of permissions from the user who tried to run the DROP command to remove the underlining HDFS path. Check HMS server log to see if you can find any error messages. ... View more

It is better to extend the varchar's length from default 4000 to, say 10000, or 20000, than changing it to clob. The reason being that VARCHAR type is well tested and supported, but CLOB is not, so we won't be sure what issues you will hit if you change the data type in the underlining database. ... View more

I was thinking about UDP vs TCP, but looks like you already have udp_preference_limit=1, so TCP always being used. You mentioned that ""quickstart.cloudera" is in the hosts file. ", can you confirm if you have tested to ping quickstart.cloudera or telnet to port 88 of host quickstart.cloudera? Have you also check your firewall rules to see if it is blocking port 88 that is used by KDC? ... View more

So we have two krb5.ini files, from the timestamp and file size, I assume that they are the same file? ... View more

This looks OK. However, I have noticed before that sometimes Windows machine can have different types of kerberos client installed and their configuration can be stored on different locations. So another thing to check is scan how many krb5.ini or krb5.conf files you have in your Windows machine and confirm which one is being used. ... View more