[
https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767506#comment-13767506
]
Hive QA commented on HIVE-3764:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12603014/HIVE-3764.4.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 3116 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testNegativeCliDriver_mapreduce_stack_trace_hadoop20
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/733/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/733/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
> Support metastore version consistency check
> -------------------------------------------
>
> Key: HIVE-3764
> URL: https://issues.apache.org/jira/browse/HIVE-3764
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Affects Versions: 0.8.0, 0.9.0, 0.10.0, 0.11.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Fix For: 0.12.0
>
> Attachments: HIVE-3764-0.13-addional-file.patch, HIVE-3764.4.patch,
> HIVE-3764.4.patch
>
>
> Today there's no version/compatibility information stored in hive metastore.
> Also the datanucleus configuration property to automatically create missing
> tables is enabled by default. If you happen to start an older or newer hive
> or don't run the correct upgrade scripts during migration, the metastore
> would end up corrupted. The autoCreate schema is not always sufficient to
> upgrade metastore when migrating to newer release. It's not supported with
> all databases. Besides the migration often involves altering existing table,
> changing or moving data etc.
> Hence it's very useful to have some consistency check to make sure that hive
> is using correct metastore and for production systems the schema is not
> automatically by running hive.
> Besides it would be helpful to add a tool that can leverage this version
> information to figure out the required set of upgrade scripts, and execute
> those against the configured metastore. Now that Hive includes Beeline
> client, it can be used to execute the scripts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
