[
https://issues.apache.org/jira/browse/HIVE-18685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838697#comment-16838697
]
Alan Gates commented on HIVE-18685:
-----------------------------------
At upgrade any existing databases do have their catalog name set to 'hive'.
And if the client does not specify a catalog the database is assigned to hive.
So upgrades and old clients with new servers are covered.
The only situation I can see that isn't covered is if an old server is using a
new database (so the database has the catalog field, but the server does not
know to set it). This isn't a case I had considered as the database is usually
upgraded with the server. If you are concerned about this case you could
submit a patch that sets the default value to 'hive'.
> Add catalogs to Hive
> --------------------
>
> Key: HIVE-18685
> URL: https://issues.apache.org/jira/browse/HIVE-18685
> Project: Hive
> Issue Type: New Feature
> Components: Metastore, Parser, Security, SQL
> Affects Versions: 3.0.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Major
> Attachments: HMS Catalog Design Doc.pdf
>
>
> SQL supports two levels of namespaces, called in the spec catalogs and
> schemas (with schema being equivalent to Hive's database). I propose to add
> the upper level of catalog. The attached design doc covers the use cases,
> requirements, and brief discussion of how it will be implemented in a
> backwards compatible way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
