Hi Stamatis, The Metastore source build should be OK for the user once we publish the artifacts to the Maven repository successfully. For the naming conventions, mainly due to HIVE-29062 which chooses to follow the old pattern the metastore 3.0.0.
[1] https://issues.apache.org/jira/browse/HIVE-29062 [2] https://dist.apache.org/repos/dist/release/hive/hive-standalone-metastore-3.0.0/ Regards, Zhihua On 2025/07/24 16:44:42 Stamatis Zampetakis wrote: > Hello, > > During the verification of RC1 I spotted some issues that I would like > to bring up for discussion. > I don't want to clutter the main vote thread thus I opted to start a > separate thread. > > The first point is the common vote thread for both Hive and Metastore. > If we plan to release independent sources and binaries for the "two" > projects it makes more sense to hold separate votes. Currently, the > number of checks that we need to perform as a community is rather high > and takes a significant amount of time to test everything. Moreover, > from the moment that one issue pops-up, even if it is isolated in one > archive, it can stop the entire RC process; it is not possible to say > +1 here, and -1 there. > > Secondly, I tried to build the standalone metastore from the source > archive (hive-standalone-metastore-4.1.0-src.tar.gz) but the built > fails cause it has dependencies to hive (e.g., hive-storage-api). If > we don't build Hive before, the > hive-standalone-metastore-4.1.0-src.tar.gz is unusable so I don't see > the benefit in making this archive part of the release process. > Assuming that we can build the hive-standalone-metastore-4.1.0-bin > from apache-hive-4.1.0-src.tar.gz, I would suggest to drop the > hive-standalone-metastore-4.1.0-src.tar.gz at least for now. A more > subtle issue with the standalone source archive is that it doesn't > contain a README and there are no instructions on how to build the > binaries. > > More generally, the build instructions for the project are not fully > up-to-date thus I logged HIVE-29102 and HIVE-29103 for tracking > efforts towards this direction. > > Another minor issue is the naming conventions that we use for Hive and > Metastore. The metastore archives do not contain the "apache-" prefix. > Although this is not a hard requirement it is a good practice to > protect our (ASF) product branding. Interestingly once we unarchive > the content the apache prefix is present in the extracted directories. > > Best, > Stamatis >
