The hive directory isn't for installing new instances of HMS, since the HMS can't use Hive itself as its database. It's for the information schema support. So when I moved the HMS schemas over into standalone-metastore I didn't move the hive directory, as it served a different purpose. I agree it would be better to make that clear in the source tree.
Alan. On Mon, Jan 13, 2020 at 1:51 AM Zoltan Chovan <zcho...@cloudera.com.invalid> wrote: > Hi all, > > I've recently done some work on the Hive database schema/upgrade files and > found the following: > > - there are two locations where we store the schema/upgrade files: > - hive/metastore/scripts/upgrade (old) > - hive/standalone-metastore/metastore-server/src/main/sql (new) > - the old location includes the 'hive' folder and the hive database > schema (this schema includes the sys and infromation_schema databases) > - the new location is missing this entirely > - looking at the packaging target directory the hive schema makes it's > way in there as the directory > > > 'hive/packaging/target/apache-hive-4.0.0-SNAPSHOT-bin/apache-hive-4.0.0-SNAPSHOT-bin/scripts/metastore/upgrade' > includes the hive folder with the schema and upgrade scripts > > > With all this I'm a bit confused why the hive folder is not in the > standalone-metastore module. Could someone shed some light on this? > > Thanks, > Zoltan >
