Dear all,
thank you for the great discussion in the last Catalog community sync,
sorry I couldn't be there.
I worked some results of the discussion into the proposal, most
importantly, the TableMetadata was removed from the create & register table
and create view events. It is easy to add this as
There are currently no open change requests that I am aware of.
I would ask all interested parties to review the current proposal and post
open points here or bring them up in the Catalog sync tomorrow.
Kevin (thanks!) will moderate this topic tomorrow as I am travelling and
probably won't make it
Hi
I think Christian updated the spec with the latest discussion
(especially about actor object).
I would suggest making a new review and maybe sync-up during the next
Catalog Community meeting.
Regards
JB
On Sat, Jun 14, 2025 at 1:18 AM Adnan Hemani
wrote:
>
> Hi all,
>
> Wanted to see if ther
Hi all,
Wanted to see if there were any remaining action items or discussions remaining
on this topic. I’m trying to get a gauge of how close we might be on getting
this merged!
Best,
Adnan Hemani
On 2025/05/28 17:33:20 Christian Thiel wrote:
> Thank you all for the great discussion today!
> I
Thank you all for the great discussion today!
I have updated the proposal. Key changes are:
-
Specify that clients should ignore unknown operation & event types
-
Specify the `actor` field as part of the `Event` schema as an opaque
string. Remove the `Actor` type.
- Remove the
Dear all,
I think we have reached mostly consensus here.
There is one more change since our last discussion: We removed the
recursive "assumed-by" field of actors in favor or an "actor-chain" list.
If there is any more need for discussion please voice it here on the
Mailing List or in the Catalog
Dear all,
I worked the changes discussed in the last catalog sync into the Events
proposal [1].
Those include:
- Using request-id instead of transaction
- A more flexible User (now called Actor)
- Custom Operation type
The specific diff compared to the last discussion can be best seen in my
lates
Dear all,
after the last Catalog sync I updated the proposal.
Changes are in the original proposal Document [1] and the original PR [2]
Best,
Christian
[1]
https://docs.google.com/document/d/1WtIsNGVX75-_MsQIOJhXLAWg6IbplV4-DkLllQEiFT8/edit?usp=sharing
[2] https://github.com/apache/iceberg/pull/1
Dear all,
We have recently discussed in the Iceberg Catalog Community Sync [1] and
the Mailing List [2] different ways on how federation between Catalogs
could be standardized.
This proposal introduces a /events endpoint to the IRC specification. The
endpoint provides events of modifications to o
