hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-4897) Hive should handle AlreadyExists on retries when creating tables/partitions
Date Sat, 08 Aug 2015 00:34:45 GMT


Sergey Shelukhin commented on HIVE-4897:

Hmm... wouldn't it just retry after the first exception and then ignore the repeated exception
on retry?
I think it may need to check that the object in question exists for each API and maybe that
it matches the request, on retry.
I am not sure there's good way to add repeatable test for this...

> Hive should handle AlreadyExists on retries when creating tables/partitions
> ---------------------------------------------------------------------------
>                 Key: HIVE-4897
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Aihua Xu
>         Attachments: HIVE-4897.patch, hive-snippet.log
> Creating new tables/partitions may fail with an AlreadyExistsException if there is an
error part way through the creation and the HMS tries again without properly cleaning up or
checking if this is a retry.
> While partitioning a new table via a script on distributed hive (MetaStore on the same
machine) there was a long timeout and then:
> {code}
> FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. AlreadyExistsException(message:Partition
already exists:Partition( ...
> {code}
> I am assuming this is due to retry. Perhaps already-exists on retry could be handled
> A similar error occurred while creating a table through Impala, which issued a single
createTable call that failed with an AlreadyExistsException. See the logs related to table
tmp_proc_8_d2b7b0f133be455ca95615818b8a5879_7 in the attached hive-snippet.log

This message was sent by Atlassian JIRA

View raw message