[ 
https://issues.apache.org/jira/browse/HIVE-26537?focusedWorklogId=854193&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-854193
 ]

ASF GitHub Bot logged work on HIVE-26537:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/Mar/23 13:12
            Start Date: 31/Mar/23 13:12
    Worklog Time Spent: 10m 
      Work Description: saihemanth-cloudera commented on code in PR #3599:
URL: https://github.com/apache/hive/pull/3599#discussion_r1154460254


##########
standalone-metastore/metastore-common/src/main/thrift/hive_metastore.thrift:
##########
@@ -2451,19 +2497,24 @@ service ThriftHiveMetastore extends 
fb303.FacebookService
   void drop_catalog(1: DropCatalogRequest catName) throws 
(1:NoSuchObjectException o1, 2:InvalidOperationException o2, 3:MetaException o3)
 
   void create_database(1:Database database) throws(1:AlreadyExistsException 
o1, 2:InvalidObjectException o2, 3:MetaException o3)

Review Comment:
   I thought we are planning to keep the backward compatibility with the old 
client and a new server for at least one release. So that's the reason why I'm 
keeping the deprecated APIs. Should I just delete them?





Issue Time Tracking
-------------------

    Worklog Id:     (was: 854193)
    Time Spent: 6h 10m  (was: 6h)

> Deprecate older APIs in the HMS
> -------------------------------
>
>                 Key: HIVE-26537
>                 URL: https://issues.apache.org/jira/browse/HIVE-26537
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 4.0.0-alpha-1, 4.0.0-alpha-2
>            Reporter: Sai Hemanth Gantasala
>            Assignee: Sai Hemanth Gantasala
>            Priority: Critical
>              Labels: hive-4.0.0-must, pull-request-available
>          Time Spent: 6h 10m
>  Remaining Estimate: 0h
>
> This Jira is to track the clean-up(deprecate older APIs and point the HMS 
> client to the newer APIs) work in the hive metastore server.
> More details will be added here soon.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to