Hi all, In addition to what christian mentioned, I need some clarification on how `additionalProperties: true` without `type : string` ( like here <https://github.com/apache/iceberg/pull/12584/files#diff-02549ca620d020dc9ead80088cc14e311e12a69651fa8d394cd41a4308debb2eR4609>) should be handled. Should I just stringify nested JSON values and put it into a String Map and let the specific implementor handle the parsing of nested values?
Regards, Ally On Tue, Dec 9, 2025 at 5:16 PM Christian Thiel <[email protected]> wrote: > Dear all, > > I would like to give a short update on the current state of the IRC Events > Endpoint: > - We have a PR open in Java for the request & response Objects (thanks > Ally) [1] > - We have a PR open in Rust for the request & response Objects [2] > - We recently got more eyes on the spec PR (Thanks Steven & Gabor!). > Resulting from the discussions in the PR and learnings from implementations > we made some changes that are summarized in comment [3] > > I would ask the community for two things: > - Please review the recent changes listed in [3] > - We need some more eyes on the Java implementation in [1] from > Maintainers, specifically on how the type > independent `CatalogObjectIdentifier` should be handled in comparison to > `Namespace`. > > I've put the topic on the Agenda for the next Catalog Community Sync and > hope that we can merge the specification soon. > > Thanks! > Christian > > [1]: Request & Response Object PR Java: > https://github.com/apache/iceberg/pull/14142 > [2]: Request & Response Object PR Rust: > https://github.com/apache/iceberg-rust/pull/1907 > [3]: Recent Changes Summary: > https://github.com/apache/iceberg/pull/12584#issuecomment-3620593088 >
