[
https://issues.apache.org/jira/browse/HIVE-18755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411634#comment-16411634
]
Alan Gates commented on HIVE-18755:
-----------------------------------
Responses to [~akolb]'s comments:
I don't think I broke wire compatibility anywhere. I made catalog required
only in newer structs that have never been in a release (like
DefaultContraintRequest) and optional in anything that has been in a release.
I can add comments to the thrift code.
CatalogName is an attempt to avoid the problem we have with Databases and
Tables and such where we are putting the string values directly in the method
calls, making it hard to add arguments to the method later. It makes
getCatalog and dropCatalog future proof.
Catalog location is the same thing as dblocation, the place where data in the
catalog will be stored. It's not optional because we have to put the data
somewhere. I could have inferred it from the catalog name, but it doesn't seem
unreasonable to require an administrator to designate a location for a catalog.
> Modifications to the metastore for catalogs
> -------------------------------------------
>
> Key: HIVE-18755
> URL: https://issues.apache.org/jira/browse/HIVE-18755
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: HIVE-18755.2.patch, HIVE-18755.nothrift, HIVE-18755.patch
>
>
> Step 1 of adding catalogs is to add support in the metastore.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
