[
https://issues.apache.org/jira/browse/IMPALA-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923510#comment-16923510
]
ASF subversion and git services commented on IMPALA-8797:
---------------------------------------------------------
Commit 69f7c8e1cd31519febf13637b4c9054ec9ab0423 in impala's branch
refs/heads/master from stiga-huang
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=69f7c8e ]
IMPALA-8797: Support database and table blacklist
Add catalogd and coordinator startup options for database and table
blacklist. Blacklisted dbs/tables will be skipped in loading. Users
won't see them when getting database/table list, e.g. in SHOW
DATABASES/TABLES. Dropping/creating blacklisted databases/tables/views
are not allowed too.
Implementation:
Catalogd and coordinators parses the --blacklisted_dbs and
--blacklisted_tables options in startup. Blacklist checks are added in
catalogd when loading the metadata and in coordinators when analysing
DDL requests for create/drop. Catalogd will also check blacklist when
executing DDL requests from coordinators in case their blacklists are
inconsistent.
Motivation:
By default, it's used to blacklist "sys" and "information_schema"
databases from Hive. Admin can use them to specify any databases/tables
that are not suitable for Impala to query.
Tests:
- Add java unit tests for blacklist related functions
- Add a custom cluster test: test_blacklisted_dbs_and_tables.py
- Ran CORE tests
Change-Id: I02dbb07f8e08793b57b2a88d09b30fd32cff26dc
Reviewed-on: http://gerrit.cloudera.org:8080/14134
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Blacklist "sys" and "information_schema" databases from Hive
> ------------------------------------------------------------
>
> Key: IMPALA-8797
> URL: https://issues.apache.org/jira/browse/IMPALA-8797
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog, Frontend
> Affects Versions: Impala 3.2.0
> Reporter: bharath v
> Assignee: Quanlong Huang
> Priority: Critical
>
> HMS exposes these two databases "sys" and "information_schema" which contain
> tables that expose the underlying meta information in a queryable format.
> However, Impala cannot read them because they come with custom serde that
> Impala doesn't support.
> From a usability point of view, we should black list those databases from
> loading, so that users don't see them when querying the database list. I
> think that is reasonable because they can't query them anyway.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
