[ https://issues.apache.org/jira/browse/HIVE-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661883#comment-14661883 ]
Hive QA commented on HIVE-4897: ------------------------------- {color:red}Overall{color}: -1 no tests executed Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12749104/HIVE-4897.patch Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4859/testReport Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4859/console Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-4859/ Messages: {noformat} Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Tests exited with: ExecutionException: java.util.concurrent.ExecutionException: java.io.IOException: Error writing to /data/hive-ptest/working/scratch/hiveptest-TestErrorMsg.sh {noformat} This message is automatically generated. ATTACHMENT ID: 12749104 - PreCommit-HIVE-TRUNK-Build > 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 > 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 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)