It's an interesting question whether Impala should show tables that are guaranteed to be unusable at all. Doing that is a little tricky on the technical side, but it might be worth considering.
On Wed, Apr 12, 2017 at 9:51 AM, Alexander Behm <[email protected]> wrote: > I'm not aware of a table property that would have this effect. > > You could use Sentry to configure something like a Hive Role and an Impala > Role. In Impala, users that do not have privileges on a table will not see > that table. A user could have one of the roles or both. Users that have > both roles would still see that error. Not sure if this approach works in > your case. > > Alex > > On Wed, Apr 12, 2017 at 5:48 AM, Petter von Dolwitz (Hem) < > [email protected]> wrote: > >> Hi, >> >> we work in environment where we use both Hive and Impala and where these >> two tools share the same metastore. Some of the tables are only usable from >> Hive since they are backed by a file format that is not supported by Impala. >> >> If a user would try to access such a table from Impala he/she would get >> the message >> >> AnalysisException: Failed to load metadata for table: 'mydb.mytable' >> CAUSED BY: TableLoadingException: Unrecognized table type for table: >> mydb.mytable >> >> We are looking for a way to hide entire DBs and/or Tables and views from >> Impala that are only usable from Hive. Anyone know a way to accomplish this? >> >> I would guess a way to support it (if not all ready present) is to add a >> db or table property signaling this fact. Another way would be to configure >> Sentry to achieve the same thing but we are not sure on how to do this. >> >> Any help is appreciated! >> >> Br, >> Petter >> >> >> >> >
