Ok, I figured it out. There was a mapping rule that translated my Kerberos principal name to a lower-case short name, i.e. USER1@EXAMPLE.COM becomes user1 I had entered both USER1 and USER1@EXAMPLE.COM as HBase superusers, but not user1. Tricky. . . ... View more

I found the solution for this issue. we can resolve the issue in following two ways. 1) we have to setfacl for 'rwx' permission for the directory from where we loading the data.   Or 2) give 777 access permission for the directory from where we loading the data.   Option1 is safer because only hive user have 'rwx' permission. In second option all the hdfs users will have 'rwx' permissions. ... View more

You will need to use both dot notation and join notation:   https://www.cloudera.com/documentation/enterprise/5-9-x/topics/impala_complex_types.html   When complex types are nested inside each other, you use a combination of joins, pseudocolumn names, and dot notation to refer to specific fields at the appropriate level. This is the most frequent form of query syntax for complex columns, because the typical use case involves two levels of complex types, such as an ARRAY of STRUCT elements. SELECT id, phone_numbers.area_code FROM contact_info_many_structs INNER JOIN contact_info_many_structs.phone_numbers phone_numbers LIMIT 3; You can express relationships between ARRAY and MAP columns at different levels as joins. You include comparison operators between fields at the top level and within the nested type columns so that Impala can do the appropriate join operation. ... View more

@David_Schwab it was my understanding that when submitting a job with a keytab, the spark Application Master would periodically renew the ticket using the principal and keytab, as per:   https://www.cloudera.com/documentation/enterprise/5-15-x/topics/cm_sg_yarn_long_jobs.html   Could it be possible that the ticket refresh rate is longer than that of the maximum ticket life? ... View more