[
https://issues.apache.org/jira/browse/HIVE-23931?focusedWorklogId=600940&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-600940
]
ASF GitHub Bot logged work on HIVE-23931:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/May/21 16:01
Start Date: 23/May/21 16:01
Worklog Time Spent: 10m
Work Description: ashish-kumar-sharma edited a comment on pull request
#2211:
URL: https://github.com/apache/hive/pull/2211#issuecomment-846585770
@kgyrtkirk
struct UniqueConstraintsRequest {
1: TableReference table;
}
Above change will not be compatible with older HMS client. Should I go
ahead and implement the above change as part of this PR or Should I create a
epic for cleaning up the deprecated api in metastore and move all api to
request model where we can have common models for multiple api?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 600940)
Time Spent: 2h (was: 1h 50m)
> Send ValidWriteIdList and tableId to get_*_constraints HMS APIs
> ---------------------------------------------------------------
>
> Key: HIVE-23931
> URL: https://issues.apache.org/jira/browse/HIVE-23931
> Project: Hive
> Issue Type: Sub-task
> Reporter: Kishen Das
> Assignee: Ashish Sharma
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Send ValidWriteIdList and tableId to get_*_constraints HMS APIs. This would
> be required in order to decide whether the response should be served from the
> Cache or backing DB.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
