[
https://issues.apache.org/jira/browse/HIVE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377293#comment-16377293
]
Alan Gates commented on HIVE-18775:
-----------------------------------
Schematool knows to look in <metastorehome>/scripts/metastore/upgrade due to
some code in the pom.xml. We could put something in the pom to copy both older
derby files from metastore and newer ones from standalone-metastore to a
directory in target and direct the tests to use scripts from there. This would
avoid needing two copies of the file.
On whether the changes broke schematool for other databases, no, because I made
sure that in the distribution they land in the same directory they used to. So
when a user untars the distribution all the .sql files will end up in the same
directory they did before. I tested that that all works.
> 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)
