Hi Kris, We use version 1.2.1 because the part that we're using hasn't changed much and we want to ensure compatibility with old metastore versions. Iceberg should work with newer metastores, and feel free to open a bug if you find a problem with one. We'll make sure to fix it to be compatible with a range of versions.
I'm not sure what people are going to want eventually. Right now, we know that many people use the Hive metastore to track tables, so it makes sense to support it as an option. Iceberg allows you to plug in your own metastore easily because we know that lots of places (Netflix included) have their own metastore implementations. I'd really love to see a new metastore project, but I don't think that Iceberg should be opinionated about which one you use. rb On Wed, Jan 29, 2020 at 7:32 AM Kristopher Kane <kk...@etsy.com.invalid> wrote: > Hi Iceberg. > > It looks like for most cases where non-atomic rename is required, using > the Hive metastore is the baseline with the ability to implement a custom. > > I couldn't find mailing list history or GitHub issue that suggests that > Iceberg will implement its own. Is that intended for the future? > > I ask because Iceberg's metastore version pin is 1.2.1 which is very old. > Someone using Iceberg, with a Hive metastore, mind find difficult moving > maintaining peace in upgrades with Hive. > > Related: Is the intention here that existing Hive users would use the > store that they have and new Iceberg users would implement custom? > > Appreciate help in understanding, > > Kris > -- Ryan Blue Software Engineer Netflix
