[ 
https://issues.apache.org/jira/browse/FLINK-34914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yubin Li updated FLINK-34914:
-----------------------------
    Description: As the application scenario of `Catalog` expands, which widely 
applied in services such as JDBC/Hive/Paimon, `Catalog` plays an increasingly 
crucial role in Flink. 
[FLIP-436|https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax]
 introduces the DQL syntaxes to obtain detailed metadata from existing 
catalogs, and the DDL syntaxes to modify metadata such as properties or comment 
in the specified catalog.  (was: As the application scenario of `Catalog` 
expands, which widely applied in services such as JDBC, Hive and Paimon, 
`Catalog` plays an increasingly crucial role in Flink. 
[FLIP-436|https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax]
 introduces the DQL syntaxes to obtain detailed metadata from existing 
catalogs, and the DDL syntaxes to modify metadata such as properties or comment 
in the specified catalog.)

> FLIP-436: Introduce Catalog-related Syntax
> ------------------------------------------
>
>                 Key: FLINK-34914
>                 URL: https://issues.apache.org/jira/browse/FLINK-34914
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / API
>    Affects Versions: 1.20.0
>            Reporter: Yubin Li
>            Assignee: Yubin Li
>            Priority: Major
>             Fix For: 1.20.0
>
>
> As the application scenario of `Catalog` expands, which widely applied in 
> services such as JDBC/Hive/Paimon, `Catalog` plays an increasingly crucial 
> role in Flink. 
> [FLIP-436|https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax]
>  introduces the DQL syntaxes to obtain detailed metadata from existing 
> catalogs, and the DDL syntaxes to modify metadata such as properties or 
> comment in the specified catalog.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to