[
https://issues.apache.org/jira/browse/IMPALA-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923417#comment-16923417
]
Quanlong Huang commented on IMPALA-8797:
----------------------------------------
Finally found something useful in
https://issues.apache.org/jira/browse/HIVE-16941
In my env (with Hive3), I just need to run
{code:bash}
schematool -metaDbType mysql -dbType hive -initSchema -url
jdbc:hive2://localhost:11050/default -driver org.apache.hive.jdbc.HiveDriver
{code}
11050 is the port of my HiveServer2.
Then the "sys" and "information_schema" databases show up in Hive.
> 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]
