You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "David Mollitor (Jira)" <ji...@apache.org> on 2021/05/21 15:12:00 UTC
[jira] [Updated] (HIVE-25144) Add NoReconnect Annotation to
CreateXXX Methods With AlreadyExistsException
[ https://issues.apache.org/jira/browse/HIVE-25144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Mollitor updated HIVE-25144:
----------------------------------
Summary: Add NoReconnect Annotation to CreateXXX Methods With AlreadyExistsException (was: Add NoReconnect Annotation to Create AlreadyExistsException Methods)
> Add NoReconnect Annotation to CreateXXX Methods With AlreadyExistsException
> ---------------------------------------------------------------------------
>
> Key: HIVE-25144
> URL: https://issues.apache.org/jira/browse/HIVE-25144
> Project: Hive
> Issue Type: Improvement
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I have recently seen an issue where a Hive {{CREATE TABLE}} method fails with {{AlreadyExistsException}} even though the table does absolutely not exist.
>
> I believe the issue is there there is a timeout/transient error with HMS and the backend database. So, the client submits the request to HMS, and the request does eventually succeed, but only after the connection to the client connects. Therefore, when the HMS Client "retry" functionality kicks it, the second time around, the table looks like it already exists.
>
> If something goes wrong during a HMS CREATE operation, we do not know the state of the operation and therefore it should just fail.
>
> It would certainly be more transparent to the end-user what is going on. An {{AlreadyExistsException}} is confusing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)