Most compute engines store view metadata in proprietary formats, which prevents sharing view definitions across platforms. Paimon views solve this by abstracting the query dialect of specific engines and establishing a unified metadata standard. This mechanism centralizes view management, enables cross-engine sharing, and reduces maintenance complexity in heterogeneous environments.
How it works
A Paimon view is a logical table that encapsulates business logic.
Manage views
Use standard SQL Data Definition Language (DDL) statements to create and delete Paimon views.
Create or replace a view
Run CREATE VIEW or CREATE OR REPLACE VIEW to register a view. The system assigns a universally unique identifier (UUID), writes the initial metadata file, and sets the version number to 1.
CREATE VIEW `paimon_catalog`.`default`.`sales_view` AS
SELECT region, SUM(amount) AS total_amount
FROM `paimon_catalog`.`default`.`sales`
GROUP BY region;Always use the fully qualified name—catalog.database.object—when creating or querying a view. Omitting any component can cause errors across different environments.
View created views in the console
-
In the navigation pane on the left, choose Data Catalog, then click the name of your catalog to open its details page.
-
Click the name of the database to open the database details page.
-
Click the Views tab.
Delete a view
DROP VIEW `paimon_catalog`.`default`.`sales_view`;Modify a view's SQL dialect
Call a system stored procedure to modify the SQL dialect associated with a view. This supports cross-engine migration and lets you target a specific execution engine.
For the full procedure reference, see Alter view dialect via procedure in the Apache Paimon documentation.