Hey, IIUC your question correctly, this is a limitation. IMPALA-2177 looks to be the appropriate jira. Most users use Impala together with Sentry, where the recommended approach is to disable impersonation (even in services that allow it, like Hive).
HTH On Wed, 2 Jan 2019 at 05:55, 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?
