Hi Dennis,

Thanks for starting this discussion!

The proposed time slot is generally OK for me, but what weekday do you
have in mind? I wouldn't be able to attend on some weekdays.

Other than that, I was wondering how much of the Catalog Federation
work would have to be built on top of a yet-to-be-created notification
/ event system. This topic has been mentioned already in 2 Polaris dev
mailing list threads:

https://lists.apache.org/thread/48fczg6okw9mos94o90tr347fbz9qc3b
https://lists.apache.org/thread/03yz5wolkvy8l7rbcwjnqdq1bl8p065v

Besides, you also sparked a very interesting discussion on the Iceberg
dev mailing list a while ago where these 2 topics were intertwined:

https://lists.apache.org/thread/zcv6qm9ysknrhfpg093qgnrkrolptcht

So, maybe one of the first items that we need to discuss here is the
notification mechanism to use to synchronize between catalogs. Wdyt?

Thanks,

Alex


On Fri, Jan 10, 2025 at 3:36 AM Dennis Huo <huoi...@gmail.com> wrote:
>
> Hello!
>
> I wanted to kick off next steps to drive forward the design discussion for
> Polaris Catalog Federation:
> https://docs.google.com/document/d/1Q6eEytxb0btpOPcL8RtkULskOlYUCo_3FLvFRnHkzBY/edit?tab=t.0
>
> In some of the prior community syncs I think folks expressed a desire to
> have some dedicated discussion time on the linked proposal and other
> related considerations. Tentatively, would 9AM Pacific (GMT-8) (6PM CET
> GMT+1) work for any folks who are interested in participating?
>
> I'd also like to use this thread to preemptively gather key areas folks
> want to cover in the discussion so that we can make the best use of
> everyone's time. Please feel free to respond with any suggestions on open
> design questions, missing areas of consideration, etc., you'd like to cover.
>
> Otherwise, any input regarding timing of this design meeting, a simple +1
> to indicate interest in participating, or even suggestions for a different
> time would be much appreciated so we can ensure an inclusive quorum of
> interested parties.
>
> Cheers,
> Dennis

Reply via email to