[
https://issues.apache.org/jira/browse/HIVE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375892#comment-16375892
]
Vineet Garg commented on HIVE-18775:
------------------------------------
Investigation into test failure reveals that schemaTool expects to find schema
file under <metastorehome>/scripts/metastore/upgrade (e.g.
MetaStoreSchemaInfo::getMetaStoreScriptDir has path hardcoded). So moving
{{hive-schema-3.0.0.derby.sql}} to different path results in bunch of test
failure (same for upgrade-2.3.0-to-3.0.0.derby.sql). In short moving these
files will break schemaTool.
[~alangates] Could HIVE-17983 have broken schema tool for other databases with
the move of schema files to different path?
> HIVE-17983 missed deleting
> metastore/scripts/upgrade/derby/hive-schema-3.0.0.derby.sql
> --------------------------------------------------------------------------------------
>
> Key: HIVE-18775
> URL: https://issues.apache.org/jira/browse/HIVE-18775
> Project: Hive
> Issue Type: Bug
> Reporter: Vineet Garg
> Assignee: Vineet Garg
> Priority: Major
> Attachments: HIVE-18775.1.patch, HIVE-18775.2.patch
>
>
> HIVE-17983 moved hive metastore schema sql files for all databases but derby
> to standalone-metastore. As a result there are not two copies of
> {{hive-schema-3.0.0.derby.sql}}.
> {{metastore/scripts/upgrade/derby/hive-schema-3.0.0.derby.sql}} needs to be
> removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
