[
https://issues.apache.org/jira/browse/HIVE-18755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412282#comment-16412282
]
Thejas M Nair commented on HIVE-18755:
--------------------------------------
On the lines of what Alexander said, I think it makes sense to create a
GetCatalogReq object and DropCatalogReq objects for use in get_catalog and
drop_catalog methods respectively. You might have arguments that are specific
to drop_catalog in future (eg "cascade=true").
Similarly even for create_catalog, having a CreateCatalogReq object would help
to keep it future proof. Now thinking on those lines, I think its simpler are
more consistent to use *Req and *Response objects as far as possible.
> 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)
