Here are the steps I follow to reproduce the issue: 1- kinit admin 2- beeline 3- !connect jdbc:hive2://cdh-dev:21050/;principal=impala/cdh-...@example.com 4- invalidate metadata; 5- select * from sample_data_4_no_token;
Attached you can find log snippets from impalad.INFO and catalogd.INFO right after step 5 above. On Tue, Jan 1, 2019 at 8:55 PM Bharath Vissapragada <bhara...@cloudera.com> wrote: > Hi, > > Can you add the stack trace here if possible? It is not super clear where > exactly the problem is. > > Thanks, > Bharath > > On Tue, Jan 1, 2019 at 6:34 PM mhd wrk <mhdwrkoff...@gmail.com> wrote: > >> we have our own implementation of Hadoop FileSystem which relies on >> current user in a kerberosied environment to locate user specific files in >> HDFS. This custom file system works fine inside hive to create external >> tables and query them. However trying to access the same tables via Impala >> (jdbc driver) fails. Watching the log messages seems that when impalad >> sends requests to catalogd to get meta data of a given table the current >> user returned by UserGroupInformation is the service account running the >> server (impala/hostn...@example.com) instead of the currently connected >> user. >> >> Is this a known issue or limitation of Impala? >> >
impalad.INFO
Description: Binary data
catalogd.INFO
Description: Binary data
