[
https://issues.apache.org/jira/browse/HIVE-6666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938540#comment-13938540
]
Hive QA commented on HIVE-6666:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12635016/HIVE-6666.1.patch
{color:green}SUCCESS:{color} +1 5397 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1862/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1862/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12635016
> Metastore init scripts should always populate the version information at the
> end
> --------------------------------------------------------------------------------
>
> Key: HIVE-6666
> URL: https://issues.apache.org/jira/browse/HIVE-6666
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.13.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Attachments: HIVE-6666.1.patch, HIVE-6666.1.patch
>
>
> The metastore schema create scripts for 0.13 and 0.14 (current trunk) has
> multiple other operations after setting the schema version. This is
> problematic as any failure in those later operations would leave metastore
> in inconsistent state, and yet with valid version information. The schemaTool
> depends on the schema version details.
> Recording the schema version should be the last step in schema initialization
> script.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
