+1 I am happy to see this progressing and aligns with the spirit of having a truly standalone HMS.
On Fri, Jul 4, 2025 at 12:18 AM Simhadri G <simhad...@apache.org> wrote: > +1 on releasing hms and the docker image. > > There is a lot of interest for standalone hms. I think we should release > it in 4.1. > > > > On Fri, Jul 4, 2025, 12:16 PM Cheng Pan <pan3...@gmail.com> wrote: > >> +1 (non-binding) >> >> This is definitely good news that the Hive community is moving forward on >> separating the HMS. >> >> The catalog service plays an essential role in a typical data platform - >> one >> catalog service, with various computing engines, table formats and >> storages. >> >> HMS is the de facto catalog service for Hadoop-based Data Warehouse, and >> I believe it is still competitive compared to new projects like Unity >> Catalog and >> Apache Polaris. >> >> Moving HMS into a separate repository or even a TLP makes it more >> attractive >> and easy to be integrated with other computing engines. >> >> Thanks, >> Cheng Pan >> >> On 2025/07/01 14:33:31 Denys Kuzmenko wrote: >> > Hi All, >> > >> > Please vote on whether we should proceed with releasing a tarball and a >> > Docker image for the Hive Metastore (HMS) as part of the Hive 4.1 >> release. >> > >> > *Context*: >> > >> > There was a concern raised in HIVE-29052 [1], suggesting that the >> current >> > packaging approach is flawed and proposing that HMS tarball should not >> be >> > released in 4.1. >> > >> > To ensure complete functionality, the HMS tarball includes hive-exec-[ >> > *core]* and hive-iceberg-handler jars. While HMS is not a standalone >> > project and likely won’t be in the foreseeable future, I don’t believe >> this >> > should block the release. >> > >> > Making HMS a truly standalone component would require a major refactor >> and >> > substantial reorganization of modules and class dependencies, work that >> has >> > been stalled for several years. >> > >> > Moreover, we need to release the HMS IcebergCatalog now to prevent users >> > from shifting to alternative catalog implementations, which risks >> rendering >> > HMS obsolete. >> > >> > Offering users a 458MB Hive tarball instead of a 169MB HMS parcel isn’t >> > ideal. Many are reluctant to download the full Hive bundle just to >> access >> > HMS binaries. >> > >> > While improvements can be made in the future, releasing a dedicated HMS >> > package now provides a solid foundation and immediate value to users. >> > >> > *Please vote*: >> > >> > +1 - Proceed with releasing the HMS tarball and Docker image in 4.1 >> > 0 - No strong opinion >> > -1 - Do not release the HMS tarball and Docker image in 4.1 (please >> explain >> > why) >> > >> > [1] >> > >> https://issues.apache.org/jira/browse/HIVE-29052?focusedCommentId=17987183&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17987183 >> >> >> >>
