Hi Peter, Thanks for bringing it up!
I think that option 1 is the only viable solution here (remove the hive-runtime from the iceberg repo). Main reason: lack of reviewers for things other than Spark. Note: need to double check, but I am pretty sure there is no difference between Hive `iceberg-catalog` and iceberg's `hive-metastore`, so we could potentially drop it from Hive repo and maybe rename to `hive-catalog` in iceberg? Supporting one more connector repo seems like an overhead: need to setup infra, CI, have active contributors/release managers. Later probably is the reason why we still haven't moved HMS into a separate repo. Having iceberg connector in Hive gives us more flexibility and ownership of that component, doesn't block an active development. We try to be up-to-date with latest iceberg, but it usually takes some time. I'd be glad to hear other opinions. Thanks, Denys
