[
https://issues.apache.org/jira/browse/HIVE-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312966#comment-14312966
]
Alan Gates commented on HIVE-9578:
----------------------------------
I think we should have a more fundamental discussion first. Is it or isn't it
this layer's problem to check that an object already exists when alter is
called? I am asserting that it is not. alterTable has already been
implemented that way. There's no denying this can lead to errors as developers
could produce code paths that forget to check for the existence of an object
first. This is especially true given that many 3rd party systems use the
Thrift interface directly. On the flip side, there is a cost of doing this
check (even for checkAndPut, which I'm sure is more expensive than a straight
put and also costs time to serialize the existing object to send for the
comparison). Since my main thrust here is performance I'm proposing to push
this cost up to the upper layers (which in general are bearing it already).
> Add support for getDatabases and alterDatabase calls [hbase-metastore branch]
> -----------------------------------------------------------------------------
>
> Key: HIVE-9578
> URL: https://issues.apache.org/jira/browse/HIVE-9578
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: HIVE-9578.patch
>
>
> The initial patch only supporting getting a single database, add database,
> and drop database. Support needs to be added for alter database, getting all
> the databases, and getting database names by pattern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
