You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sai Hemanth Gantasala (Jira)" <ji...@apache.org> on 2023/05/05 16:39:00 UTC

[jira] [Updated] (HIVE-27319) HMS server should throw InvalidObjectException in get_partitions_by_names() when the table is missing/dropped

     [ https://issues.apache.org/jira/browse/HIVE-27319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sai Hemanth Gantasala updated HIVE-27319:
-----------------------------------------
    Summary: HMS server should throw InvalidObjectException in get_partitions_by_names() when the table is missing/dropped  (was: HMS server should throw InvalidObjectException when the table is missing in get_partitions_by_names())

> HMS server should throw InvalidObjectException in get_partitions_by_names() when the table is missing/dropped
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-27319
>                 URL: https://issues.apache.org/jira/browse/HIVE-27319
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive, Standalone Metastore
>            Reporter: Sai Hemanth Gantasala
>            Assignee: Sai Hemanth Gantasala
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When the table object is dropped by a concurrent thread, the get_partitions_by_names_req() API is currently throwing a TApplicationException to the client. Instead, the HMS server should propagate the InvalidObjectException thrown by getTable() to the HMS client. By doing this, other services using HMS client will understand the exception better.



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