Hi All, Let me chime in here and add some Hive perspective on that.
The only reason Iceberg support has moved into Hive, is that we didn't get enough support from the existing community. Our PRs got stuck pending review and even if we got some +1 those were not binding. Don't take me wrong, it is what it is, I am not blaming anyone, just trying to shed some light on things from our side. To progress, the only option for us was to move the bits in Hive hoping we could contribute them back later: Hive 4 integration, MV support, advanced column statistics, vectorization, caching, etc. Since we don't have Hive representatives in the iceberg community it became painful and frustrating. We are eager to contribute, but the lack of support stopped us from even considering that. Our original goal was(is) to move iceberg-catalog and handler modules from Hive back to iceberg, but we would need some help here. We are actively working on jdk17 migration, hoping to keep at least the existing hive-connector in iceberg repo. If hive-iceberg modules are dropped, Hive-3 won't have any upgrade path, and based on stats it remains the most actively used version. Kind regards, Denys
