hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-16723) Enable configurable MetaStoreSchemaInfo
Date Sun, 21 May 2017 06:38:04 GMT


Hive QA commented on HIVE-16723:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 4 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 10743 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[compute_stats_boolean] (batchId=78)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[parquet_ppd_decimal] (batchId=9)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.

ATTACHMENT ID: 12869153 - PreCommit-HIVE-Build

> Enable configurable MetaStoreSchemaInfo 
> ----------------------------------------
>                 Key: HIVE-16723
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>         Attachments: HIVE-16723.01.patch, HIVE-16723.02.patch, HIVE-16723.03.patch
> {{MetaStoreSchemaInfo}} class is used by Schema tool to get the schema version information.
In addition to that schema tool invokes its init and upgrade methods to initialize and upgrade
the metastore schema. It is possible that there are minor schema changes in the metastore
schema which users have to maintain manually. We can potentially enhance schema tool to use
a custom MetaStoreSchemaInfo implementation which can be plugged in based on configuration
and schematool could run these customizations while running the upgrade and init scripts.

This message was sent by Atlassian JIRA

View raw message