[
https://issues.apache.org/jira/browse/HIVE-18755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408812#comment-16408812
]
Alan Gates commented on HIVE-18755:
-----------------------------------
Peter, I think I understood your intent from the first question, which I
believe was: "why not always handle the missing catalog on the server side?"
To which my answer is, I am trying to always handle the missing catalog on the
server side, so that it is compatible with old clients. But I am also handling
the missing catalog on the client side (like my change in DDLTask.java) so that
if the metastore server is set up to talk to one catalog but users want to
configure their clients to talk to another by default without changing every
one of their client calls to use the new catalog aware method, they can. So
for example, say someone has a Hive CLI client they are using and they want to
default to 'mycatalog' instead of whatever their metastore server is set to.
They can then set that value in their config file and it will still work, even
though I haven't changed every call to getTable etc inside Hive.
> 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.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)
