Hi all, I'd like to start a discussion on the design of view management in Gravitino, tracked under the epic #604 (https://github.com/apache/gravitino/issues/604).
Problem: Views are a fundamental abstraction in data lakehouses, yet view management today is fragmented — views are scattered across different metastores and engines with no unified way to manage, govern, or share them across the data platform. Proposal: Add a unified view management layer to Gravitino with multi-engine visibility (through multi-dialect SQL representation storage), capability-driven storage strategy per catalog type (Iceberg, HMS, JDBC, etc.), and governance integration (access control, audit, events). This builds on the existing IRC view support in Gravitino 1.2. The detailed design document and issue are here: - GitHub Issue: https://github.com/apache/gravitino/issues/10588 - Design Document: https://docs.google.com/document/d/1qKZMcY5ifgZF-BjGF2FwYBNWyTwqrCDLaGW_D2jD_LY/edit?usp=sharing Feedback and suggestions are very welcome. Thanks! Best regards, Minghuang Li
