You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Matthew Jacobs (JIRA)" <ji...@apache.org> on 2015/06/30 03:27:05 UTC
[jira] [Updated] (HIVE-4897) Hive should handle AlreadyExists on
retries when creating tables/partitions
[ https://issues.apache.org/jira/browse/HIVE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Jacobs updated HIVE-4897:
---------------------------------
Priority: Major (was: Minor)
Description:
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 better.
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
was:
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 better.
Summary: Hive should handle AlreadyExists on retries when creating tables/partitions (was: Hive should handle AlreadyExists on retries when creating partitions)
> Hive should handle AlreadyExists on retries when creating tables/partitions
> ---------------------------------------------------------------------------
>
> Key: HIVE-4897
> URL: https://issues.apache.org/jira/browse/HIVE-4897
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Attachments: 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 better.
> 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
(v6.3.4#6332)