Hi Leonard, Thank you for the great point. I agree that aligning on a unified system table specification — covering naming, permissions, and global/per-table view—should come first. This vote can wait until that foundation is in place. Looking forward to the discussion when it comes up on the list.
Best regards, SeungMin Lee 2026년 3월 11일 (수) PM 3:43, Leonard Xu <[email protected]>님이 작성: > Thanks SeungMin for driving this FIP. > > > Current idea that introduced system table looks good to me. > For the system table design, I'd like to involve Yang Guo in the review. > As we need to consider that system tables aren't just for lake tiering > status; we also need system table for table consumer group maintenance as > well as table schema change tracking. Yang Guo is already working on a > preliminary design covering fluss system tables. > My suggestion is to align on a unified system table specification > first—covering aspects like naming, permissions, and global/per-table > views—before we push forward with this FIP. This approach will guarantee > API consistency down the line. > WDYT? > Best, > Leonard
