The week after a major release tends to look quiet on a project's dev list. This one did not. With Iceberg 1.11.0 and 1.10.2 both out the door the week before, and Polaris 1.5.0 shipping right at the start of this window, you might have expected the lakehouse projects to take a breath. Instead the conversation shifted from "what are we shipping" to "what do we build on top of what we just shipped," and that turned out to be a busier and more interesting set of threads. Encryption moved from Iceberg core into the catalog layer. The REST spec picked up two new client-facing extensions. Arrow took a donation across the finish line and started arguing about whether a bot should review its pull requests. Parquet finally voted on a statistics change that had been circling the list for years. Taken together, the week was about the connective tissue of the lakehouse: the catalog, the protocol, the client contract, and the unglamorous governance work that keeps four independent projects interoperable.
Apache Iceberg
The single most consequential thread of the Iceberg week was procedural rather than technical. Ryan Blue posted the RESULT for the vote to add an unregister endpoint to the REST spec, which passed with 16 +1 votes, 9 of them binding, and no dissent. That is a strong mandate for what is a deceptively important capability. Until now the REST catalog has had no standard way to drop a table's registration without also deleting its data and metadata, which matters enormously for the migration and multi-catalog scenarios that Iceberg increasingly has to support. As tables move between catalogs, or as a catalog needs to hand off ownership of a table to another system, unregister is the clean primitive that makes that safe. The breadth of binding support tells you this was not controversial in substance, only in getting the wording precise enough to standardize.
