[jira] [Commented] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li commented on FLINK-34914:
--

[~Weijie Guo] Thanks for reminding that. The relevant documents have been 
merged along with these features. please see details as below:

[https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/create/#create-catalog]

[https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/show/#show-create-catalog]

[https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/describe/#describe-catalog]

[https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/alter/#alter-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)

[jira] [Comment Edited] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li edited comment on FLINK-34914 at 7/5/24 9:17 AM:
--

[~Weijie Guo] Hi, I have updated release note in the `Release note` part of 
this Jira, Do you mean this?

```

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.

```


was (Author: liyubin117):
[~Weijie Guo] Hi, I have updated release note in the `Description` part of this 
Jira, Do you mean this?

```

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 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.



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

[jira] [Comment Edited] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li edited comment on FLINK-34914 at 7/5/24 9:19 AM:
--

[~Weijie Guo] Hi, I have updated release note in the `Release note` part of 
this Jira, Do you mean this?


was (Author: liyubin117):
[~Weijie Guo] Hi, I have updated release note in the `Release note` part of 
this Jira, Do you mean this?

```

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 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.



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

[jira] [Updated] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

 [ 
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)

[jira] [Updated] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34914:
-
Release Note: 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 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 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 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.



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

[jira] [Updated] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34914:
-
Release Note: 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 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 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.



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

[jira] [Commented] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li commented on FLINK-34914:
--

[~Weijie Guo] Hi, I have updated release note in the `Description` part of this 
Jira, Do you mean this?

```

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 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.



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

[jira] [Updated] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

 [ 
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 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.  (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 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 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.



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

[jira] [Updated] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

 [ 
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 and Paimon, `Catalog` plays an 
increasingly crucial role in Flink. FLIP-436 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: 
Umbrella issue for: 
https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax)

> 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 and Paimon, `Catalog` plays an increasingly 
> crucial role in Flink. FLIP-436 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)

[jira] [Commented] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-35663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17861211#comment-17861211
 ] 

Yubin Li commented on FLINK-35663:
--

[~ferenc-csaky] Thanks for the volunteering(y)

> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Ferenc Csaky
>Priority: Blocker
> Attachments: image-2024-06-21-09-43-47-391.png, 
> image-2024-06-21-09-43-58-460.png, image-2024-06-21-09-44-26-213.png, 
> image-2024-06-21-09-45-43-807.png
>
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> ('type'='generic_in_memory', 'default-database'='db1');
> create catalog if not exists c1 comment 'new' with 
> ('type'='generic_in_memory'); 
> create catalog if not exists c2 with ('type'='generic_in_memory'); 
> create catalog c2 with ('type'='generic_in_memory', 
> 'default-database'='db2'); {code}
> Verify whether only the last statement is supposed to throw an exception and 
> messages such as `Catalog c2 already exists.`
> h3. 3. Execute the following statements.
> {code:java}
> show catalogs;
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2; {code}
> Verify whether they are the same as the given results.
> !image-2024-06-21-09-45-43-807.png|width=795,height=933!
> h3. 4. Execute the following DDL statements.
> {code:java}
> alter catalog c1 reset ('default-database');
> alter catalog c1 comment '';
> alter catalog c2 set ('default-database'='db2');
> alter catalog c2 reset ('type');
> alter catalog c2 reset ();
> alter catalog c2 comment 'hello catalog ''c2''';{code}
> Verify whether the forth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support changing 'type'`.
> Verify whether the fifth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support empty key`.
> h3. 5. Execute the following statements.
> {code:java}
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2;  {code}
> Verify whether they are the same as the given results.
> !image-2024-06-21-09-44-26-213.png|width=792,height=792!



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

[jira] [Commented] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li commented on FLINK-34914:
--

[~Weijie Guo] Surely, I will make it as soon as possible:)

> 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
>
>
> Umbrella issue for: 
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax



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

[jira] [Updated] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35663:
-
Description: 
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-21-09-45-43-807.png|width=795,height=933!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-21-09-44-26-213.png|width=792,height=792!

  was:
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-21-09-43-47-391.png!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-21-09-44-26-213.png!


> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-06-21-09-43-47-391.png, 
> image-2024-06-21-09-43-58-460.png, image-2024-06-21-09-44-26-213.png, 
> image-2024-06-21-09-45-43-807.png
>
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> 

[jira] [Updated] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35663:
-
Attachment: image-2024-06-21-09-45-43-807.png

> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-06-21-09-43-47-391.png, 
> image-2024-06-21-09-43-58-460.png, image-2024-06-21-09-44-26-213.png, 
> image-2024-06-21-09-45-43-807.png
>
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> ('type'='generic_in_memory', 'default-database'='db1');
> create catalog if not exists c1 comment 'new' with 
> ('type'='generic_in_memory'); 
> create catalog if not exists c2 with ('type'='generic_in_memory'); 
> create catalog c2 with ('type'='generic_in_memory', 
> 'default-database'='db2'); {code}
> Verify whether only the last statement is supposed to throw an exception and 
> messages such as `Catalog c2 already exists.`
> h3. 3. Execute the following statements.
> {code:java}
> show catalogs;
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2; {code}
> Verify whether they are the same as the given results.
> !image-2024-06-21-09-43-47-391.png!
> h3. 4. Execute the following DDL statements.
> {code:java}
> alter catalog c1 reset ('default-database');
> alter catalog c1 comment '';
> alter catalog c2 set ('default-database'='db2');
> alter catalog c2 reset ('type');
> alter catalog c2 reset ();
> alter catalog c2 comment 'hello catalog ''c2''';{code}
> Verify whether the forth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support changing 'type'`.
> Verify whether the fifth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support empty key`.
> h3. 5. Execute the following statements.
> {code:java}
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2;  {code}
> Verify whether they are the same as the given results.
> !image-2024-06-21-09-44-26-213.png!



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

[jira] [Updated] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35663:
-
Attachment: image-2024-06-21-09-44-26-213.png

> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-06-21-09-43-47-391.png, 
> image-2024-06-21-09-43-58-460.png, image-2024-06-21-09-44-26-213.png
>
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> ('type'='generic_in_memory', 'default-database'='db1');
> create catalog if not exists c1 comment 'new' with 
> ('type'='generic_in_memory'); 
> create catalog if not exists c2 with ('type'='generic_in_memory'); 
> create catalog c2 with ('type'='generic_in_memory', 
> 'default-database'='db2'); {code}
> Verify whether only the last statement is supposed to throw an exception and 
> messages such as `Catalog c2 already exists.`
> h3. 3. Execute the following statements.
> {code:java}
> show catalogs;
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2; {code}
> Verify whether they are the same as the given results.
> !image-2024-06-16-09-30-16-983.png|width=768,height=902!
> h3. 4. Execute the following DDL statements.
> {code:java}
> alter catalog c1 reset ('default-database');
> alter catalog c1 comment '';
> alter catalog c2 set ('default-database'='db2');
> alter catalog c2 reset ('type');
> alter catalog c2 reset ();
> alter catalog c2 comment 'hello catalog ''c2''';{code}
> Verify whether the forth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support changing 'type'`.
> Verify whether the fifth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support empty key`.
> h3. 5. Execute the following statements.
> {code:java}
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2;  {code}
> Verify whether they are the same as the given results.
> !image-2024-06-16-09-47-27-956.png|width=712,height=713!



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

[jira] [Updated] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35663:
-
Description: 
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-21-09-43-47-391.png!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-21-09-44-26-213.png!

  was:
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=768,height=902!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=712,height=713!


> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-06-21-09-43-47-391.png, 
> image-2024-06-21-09-43-58-460.png, image-2024-06-21-09-44-26-213.png
>
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> ('type'='generic_in_memory', 'default-database'='db1');
> 

[jira] [Updated] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35663:
-
Attachment: image-2024-06-21-09-43-58-460.png

> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-06-21-09-43-47-391.png, 
> image-2024-06-21-09-43-58-460.png
>
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> ('type'='generic_in_memory', 'default-database'='db1');
> create catalog if not exists c1 comment 'new' with 
> ('type'='generic_in_memory'); 
> create catalog if not exists c2 with ('type'='generic_in_memory'); 
> create catalog c2 with ('type'='generic_in_memory', 
> 'default-database'='db2'); {code}
> Verify whether only the last statement is supposed to throw an exception and 
> messages such as `Catalog c2 already exists.`
> h3. 3. Execute the following statements.
> {code:java}
> show catalogs;
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2; {code}
> Verify whether they are the same as the given results.
> !image-2024-06-16-09-30-16-983.png|width=768,height=902!
> h3. 4. Execute the following DDL statements.
> {code:java}
> alter catalog c1 reset ('default-database');
> alter catalog c1 comment '';
> alter catalog c2 set ('default-database'='db2');
> alter catalog c2 reset ('type');
> alter catalog c2 reset ();
> alter catalog c2 comment 'hello catalog ''c2''';{code}
> Verify whether the forth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support changing 'type'`.
> Verify whether the fifth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support empty key`.
> h3. 5. Execute the following statements.
> {code:java}
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2;  {code}
> Verify whether they are the same as the given results.
> !image-2024-06-16-09-47-27-956.png|width=712,height=713!



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

[jira] [Updated] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35663:
-
Attachment: image-2024-06-21-09-43-47-391.png

> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-06-21-09-43-47-391.png, 
> image-2024-06-21-09-43-58-460.png
>
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> ('type'='generic_in_memory', 'default-database'='db1');
> create catalog if not exists c1 comment 'new' with 
> ('type'='generic_in_memory'); 
> create catalog if not exists c2 with ('type'='generic_in_memory'); 
> create catalog c2 with ('type'='generic_in_memory', 
> 'default-database'='db2'); {code}
> Verify whether only the last statement is supposed to throw an exception and 
> messages such as `Catalog c2 already exists.`
> h3. 3. Execute the following statements.
> {code:java}
> show catalogs;
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2; {code}
> Verify whether they are the same as the given results.
> !image-2024-06-16-09-30-16-983.png|width=768,height=902!
> h3. 4. Execute the following DDL statements.
> {code:java}
> alter catalog c1 reset ('default-database');
> alter catalog c1 comment '';
> alter catalog c2 set ('default-database'='db2');
> alter catalog c2 reset ('type');
> alter catalog c2 reset ();
> alter catalog c2 comment 'hello catalog ''c2''';{code}
> Verify whether the forth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support changing 'type'`.
> Verify whether the fifth statement is supposed to throw an exception and 
> messages such as `ALTER CATALOG RESET does not support empty key`.
> h3. 5. Execute the following statements.
> {code:java}
> show create catalog c1;
> describe catalog c1;
> desc catalog extended c1;
> show create catalog c2;
> describe catalog c2;
> desc catalog extended c2;  {code}
> Verify whether they are the same as the given results.
> !image-2024-06-16-09-47-27-956.png|width=712,height=713!



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

[jira] [Updated] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35663:
-
Description: 
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=768,height=902!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=712,height=713!

  was:
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=671,height=788!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=679,height=680!


> Release Testing: FLIP-436: Introduce Catalog-related Syntax
> ---
>
> Key: FLINK-35663
> URL: https://issues.apache.org/jira/browse/FLINK-35663
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
>
> This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
> Syntax.
> The verification steps are as follows.
> h3. 1. Start the sql client.
> bin/sql-client.sh
> h3. 2. Execute the following DDL statements.
> {code:java}
> create catalog c1 comment 'comment for ''c1''' with 
> ('type'='generic_in_memory', 'default-database'='db1');
> create catalog if not exists c1 comment 'new' with 
> ('type'='generic_in_memory'); 
> create 

[jira] [Created] (FLINK-35663) Release Testing: FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

Yubin Li created FLINK-35663:


 Summary: Release Testing: FLIP-436: Introduce Catalog-related 
Syntax
 Key: FLINK-35663
 URL: https://issues.apache.org/jira/browse/FLINK-35663
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Affects Versions: 1.20.0
Reporter: Yubin Li


This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=671,height=788!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=679,height=680!



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

[jira] [Comment Edited] (FLINK-35621) Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-35621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855267#comment-17855267
 ] 

Yubin Li edited comment on FLINK-35621 at 6/16/24 1:53 AM:
---

This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=671,height=788!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=679,height=680!


was (Author: liyubin117):
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

 

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=671,height=788!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=679,height=680!

 

 

 

 

 

> Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related 
> Syntax
> ---
>
> Key: FLINK-35621
> URL: https://issues.apache.org/jira/browse/FLINK-35621
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Weijie Guo
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.20.0
>
> Attachments: image-2024-06-16-09-30-16-983.png, 
> image-2024-06-16-09-40-05-959.png, image-2024-06-16-09-47-27-956.png
>
>
> Follow up the test for https://issues.apache.org/jira/browse/FLINK-34914



--
This 

[jira] [Comment Edited] (FLINK-35621) Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-35621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855267#comment-17855267
 ] 

Yubin Li edited comment on FLINK-35621 at 6/16/24 1:51 AM:
---

This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

 

The verification steps are as follows.
h3. 1. Start the sql client.

bin/sql-client.sh
h3. 2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
h3. 3. Execute the following statements.
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=671,height=788!
h3. 4. Execute the following DDL statements.
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.
h3. 5. Execute the following statements.
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=679,height=680!

 

 

 

 

 


was (Author: liyubin117):
This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

 

The verification steps are as follows.
1. Start the standalone session cluster and sql client.
2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
3. Execute the following statements.

 
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=671,height=788!

4. Execute the following DDL statements.

 
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.

5. Execute the following statements.

 
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=679,height=680!

 

 

 

 

 

> Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related 
> Syntax
> ---
>
> Key: FLINK-35621
> URL: https://issues.apache.org/jira/browse/FLINK-35621
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Weijie Guo
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.20.0
>
> Attachments: image-2024-06-16-09-30-16-983.png, 
> image-2024-06-16-09-40-05-959.png, image-2024-06-16-09-47-27-956.png
>
>
> Follow up the test for 

[jira] [Commented] (FLINK-35621) Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-35621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855267#comment-17855267
 ] 

Yubin Li commented on FLINK-35621:
--

This describes how to verify FLINK-34914 FLIP-436: Introduce Catalog-related 
Syntax.

 

The verification steps are as follows.
1. Start the standalone session cluster and sql client.
2. Execute the following DDL statements.
{code:java}
create catalog c1 comment 'comment for ''c1''' with 
('type'='generic_in_memory', 'default-database'='db1');

create catalog if not exists c1 comment 'new' with 
('type'='generic_in_memory'); 

create catalog if not exists c2 with ('type'='generic_in_memory'); 

create catalog c2 with ('type'='generic_in_memory', 'default-database'='db2'); 
{code}
Verify whether only the last statement is supposed to throw an exception and 
messages such as `Catalog c2 already exists.`
3. Execute the following statements.

 
{code:java}
show catalogs;

show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2; {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-30-16-983.png|width=671,height=788!

4. Execute the following DDL statements.

 
{code:java}
alter catalog c1 reset ('default-database');

alter catalog c1 comment '';

alter catalog c2 set ('default-database'='db2');

alter catalog c2 reset ('type');

alter catalog c2 reset ();

alter catalog c2 comment 'hello catalog ''c2''';{code}
Verify whether the forth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support changing 'type'`.

Verify whether the fifth statement is supposed to throw an exception and 
messages such as `ALTER CATALOG RESET does not support empty key`.

5. Execute the following statements.

 
{code:java}
show create catalog c1;

describe catalog c1;

desc catalog extended c1;

show create catalog c2;

describe catalog c2;

desc catalog extended c2;  {code}
Verify whether they are the same as the given results.

!image-2024-06-16-09-47-27-956.png|width=679,height=680!

 

 

 

 

 

> Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related 
> Syntax
> ---
>
> Key: FLINK-35621
> URL: https://issues.apache.org/jira/browse/FLINK-35621
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Weijie Guo
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.20.0
>
> Attachments: image-2024-06-16-09-30-16-983.png, 
> image-2024-06-16-09-40-05-959.png, image-2024-06-16-09-47-27-956.png
>
>
> Follow up the test for https://issues.apache.org/jira/browse/FLINK-34914



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

[jira] [Updated] (FLINK-35621) Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35621:
-
Attachment: image-2024-06-16-09-47-27-956.png

> Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related 
> Syntax
> ---
>
> Key: FLINK-35621
> URL: https://issues.apache.org/jira/browse/FLINK-35621
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Weijie Guo
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.20.0
>
> Attachments: image-2024-06-16-09-30-16-983.png, 
> image-2024-06-16-09-40-05-959.png, image-2024-06-16-09-47-27-956.png
>
>
> Follow up the test for https://issues.apache.org/jira/browse/FLINK-34914



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

[jira] [Updated] (FLINK-35621) Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35621:
-
Attachment: image-2024-06-16-09-40-05-959.png

> Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related 
> Syntax
> ---
>
> Key: FLINK-35621
> URL: https://issues.apache.org/jira/browse/FLINK-35621
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Weijie Guo
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.20.0
>
> Attachments: image-2024-06-16-09-30-16-983.png, 
> image-2024-06-16-09-40-05-959.png
>
>
> Follow up the test for https://issues.apache.org/jira/browse/FLINK-34914



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

[jira] [Updated] (FLINK-35621) Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35621:
-
Attachment: image-2024-06-16-09-30-16-983.png

> Release Testing Instructions: Verify FLIP-436: Introduce Catalog-related 
> Syntax
> ---
>
> Key: FLINK-35621
> URL: https://issues.apache.org/jira/browse/FLINK-35621
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Weijie Guo
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.20.0
>
> Attachments: image-2024-06-16-09-30-16-983.png
>
>
> Follow up the test for https://issues.apache.org/jira/browse/FLINK-34914



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

[jira] [Updated] (FLINK-35597) Fix unstable LocatableSplitAssignerTest#testConcurrentSplitAssignmentForMultipleHosts

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35597:
-
Description: To ensure at least one fraction of hosts to be local, it 
should be {{ia.getNumberOfLocalAssignments()}} as before.

> Fix unstable 
> LocatableSplitAssignerTest#testConcurrentSplitAssignmentForMultipleHosts
> -
>
> Key: FLINK-35597
> URL: https://issues.apache.org/jira/browse/FLINK-35597
> Project: Flink
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
>  Labels: pull-request-available
>
> To ensure at least one fraction of hosts to be local, it should be 
> {{ia.getNumberOfLocalAssignments()}} as before.



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

[jira] [Created] (FLINK-35597) Fix unstable LocatableSplitAssignerTest#testConcurrentSplitAssignmentForMultipleHosts

[Yubin Li (Jira)]

Yubin Li created FLINK-35597:


 Summary: Fix unstable 
LocatableSplitAssignerTest#testConcurrentSplitAssignmentForMultipleHosts
 Key: FLINK-35597
 URL: https://issues.apache.org/jira/browse/FLINK-35597
 Project: Flink
  Issue Type: Bug
  Components: Tests
Affects Versions: 1.20.0
Reporter: Yubin Li






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

[jira] [Updated] (FLINK-34918) Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Description: 
Set comment in the specified catalog. If the comment is already set in the 
catalog, override the old value with the new one.

!image-2024-06-13-18-01-34-910.png|width=715,height=523!

  was:
We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
reasons are as follows.

1. For the sake of design consistency, follow the design of FLIP-295 [1] which 
introduced `CatalogStore` component, `CatalogDescriptor` includes names and 
attributes, both of which are used to describe the catalog, and `comment` can 
be added smoothly.

2. Extending the existing class rather than add new method to the existing 
interface, Especially, the `Catalog` interface, as a core interface, is used by 
a series of important components such as `CatalogFactory`, `CatalogManager` and 
`FactoryUtil`, and is implemented by a large number of connectors such as JDBC, 
Paimon, and Hive. Adding methods to it will greatly increase the implementation 
complexity, and more importantly, increase the cost of iteration, maintenance, 
and verification.

 

Set comment in the specified catalog. If the comment is already set in the 
catalog, override the old value with the new one.

!image-2024-06-13-18-01-34-910.png|width=715,height=523!


> Support `ALTER CATALOG COMMENT` syntax
> --
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Attachments: image-2024-06-13-18-01-34-910.png
>
>
> Set comment in the specified catalog. If the comment is already set in the 
> catalog, override the old value with the new one.
> !image-2024-06-13-18-01-34-910.png|width=715,height=523!



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

[jira] [Updated] (FLINK-34917) Introduce comment for CatalogStore & Support enhanced `CREATE CATALOG` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34917:
-
Description: 
We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
reasons are as follows.

1. For the sake of design consistency, follow the design of FLIP-295 [1] which 
introduced `CatalogStore` component, `CatalogDescriptor` includes names and 
attributes, both of which are used to describe the catalog, and `comment` can 
be added smoothly.

2. Extending the existing class rather than add new method to the existing 
interface, Especially, the `Catalog` interface, as a core interface, is used by 
a series of important components such as `CatalogFactory`, `CatalogManager` and 
`FactoryUtil`, and is implemented by a large number of connectors such as JDBC, 
Paimon, and Hive. Adding methods to it will greatly increase the implementation 
complexity, and more importantly, increase the cost of iteration, maintenance, 
and verification.

 

{{IF NOT EXISTS}}  clause: If the catalog already exists, nothing happens.

{{COMMENT}} clause: An optional string literal. The description for the catalog.

NOTICE: we just need to introduce the '[IF NOT EXISTS]' and '[COMMENT]' clause 
to the 'create catalog' statement.

!image-2024-03-22-18-31-59-632.png|width=795,height=87!

  was:
{{IF NOT EXISTS}}  clause: If the catalog already exists, nothing happens.

{{COMMENT}} clause: An optional string literal. The description for the catalog.

NOTICE: we just need to introduce the '[IF NOT EXISTS]' and '[COMMENT]' clause 
to the 'create catalog' statement.

!image-2024-03-22-18-31-59-632.png|width=795,height=87!


> Introduce comment for CatalogStore & Support enhanced `CREATE CATALOG` syntax
> -
>
> Key: FLINK-34917
> URL: https://issues.apache.org/jira/browse/FLINK-34917
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
> Attachments: image-2024-03-22-18-31-59-632.png
>
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.
>  
> {{IF NOT EXISTS}}  clause: If the catalog already exists, nothing happens.
> {{COMMENT}} clause: An optional string literal. The description for the 
> catalog.
> NOTICE: we just need to introduce the '[IF NOT EXISTS]' and '[COMMENT]' 
> clause to the 'create catalog' statement.
> !image-2024-03-22-18-31-59-632.png|width=795,height=87!



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

[jira] [Updated] (FLINK-34917) Introduce comment for CatalogStore & Support enhanced `CREATE CATALOG` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34917:
-
Summary: Introduce comment for CatalogStore & Support enhanced `CREATE 
CATALOG` syntax  (was: Support enhanced `CREATE CATALOG` syntax)

> Introduce comment for CatalogStore & Support enhanced `CREATE CATALOG` syntax
> -
>
> Key: FLINK-34917
> URL: https://issues.apache.org/jira/browse/FLINK-34917
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
> Attachments: image-2024-03-22-18-31-59-632.png
>
>
> {{IF NOT EXISTS}}  clause: If the catalog already exists, nothing happens.
> {{COMMENT}} clause: An optional string literal. The description for the 
> catalog.
> NOTICE: we just need to introduce the '[IF NOT EXISTS]' and '[COMMENT]' 
> clause to the 'create catalog' statement.
> !image-2024-03-22-18-31-59-632.png|width=795,height=87!



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

[jira] [Updated] (FLINK-34918) Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Summary: Support `ALTER CATALOG COMMENT` syntax  (was: Introduce comment 
for CatalogStore & Support `ALTER CATALOG COMMENT` syntax)

> Support `ALTER CATALOG COMMENT` syntax
> --
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Attachments: image-2024-06-13-18-01-34-910.png
>
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.
>  
> Set comment in the specified catalog. If the comment is already set in the 
> catalog, override the old value with the new one.
> !image-2024-06-13-18-01-34-910.png|width=715,height=523!



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

[jira] [Closed] (FLINK-35451) Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li closed FLINK-35451.

Resolution: Duplicate

> Support `ALTER CATALOG COMMENT` syntax
> --
>
> Key: FLINK-35451
> URL: https://issues.apache.org/jira/browse/FLINK-35451
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Reporter: Yubin Li
>Priority: Major
> Fix For: 1.20.0
>
> Attachments: image-2024-05-26-02-11-30-070.png
>
>
> Set comment in the specified catalog. If the comment is already set in the 
> catalog, override the old value with the new one.
> !image-2024-05-26-02-11-30-070.png|width=575,height=415!



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

[jira] [Updated] (FLINK-35451) Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-35451:
-
Parent: (was: FLINK-34914)
Issue Type: New Feature  (was: Sub-task)

> Support `ALTER CATALOG COMMENT` syntax
> --
>
> Key: FLINK-35451
> URL: https://issues.apache.org/jira/browse/FLINK-35451
> Project: Flink
>  Issue Type: New Feature
>  Components: Table SQL / API
>Reporter: Yubin Li
>Priority: Major
> Fix For: 1.20.0
>
> Attachments: image-2024-05-26-02-11-30-070.png
>
>
> Set comment in the specified catalog. If the comment is already set in the 
> catalog, override the old value with the new one.
> !image-2024-05-26-02-11-30-070.png|width=575,height=415!



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

[jira] [Updated] (FLINK-34918) Introduce comment for CatalogStore & Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
 Attachment: image-2024-06-13-18-01-34-910.png
Description: 
We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
reasons are as follows.

1. For the sake of design consistency, follow the design of FLIP-295 [1] which 
introduced `CatalogStore` component, `CatalogDescriptor` includes names and 
attributes, both of which are used to describe the catalog, and `comment` can 
be added smoothly.

2. Extending the existing class rather than add new method to the existing 
interface, Especially, the `Catalog` interface, as a core interface, is used by 
a series of important components such as `CatalogFactory`, `CatalogManager` and 
`FactoryUtil`, and is implemented by a large number of connectors such as JDBC, 
Paimon, and Hive. Adding methods to it will greatly increase the implementation 
complexity, and more importantly, increase the cost of iteration, maintenance, 
and verification.

 

Set comment in the specified catalog. If the comment is already set in the 
catalog, override the old value with the new one.

!image-2024-06-13-18-01-34-910.png|width=715,height=523!

  was:
We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
reasons are as follows.

1. For the sake of design consistency, follow the design of FLIP-295 [1] which 
introduced `CatalogStore` component, `CatalogDescriptor` includes names and 
attributes, both of which are used to describe the catalog, and `comment` can 
be added smoothly.

2. Extending the existing class rather than add new method to the existing 
interface, Especially, the `Catalog` interface, as a core interface, is used by 
a series of important components such as `CatalogFactory`, `CatalogManager` and 
`FactoryUtil`, and is implemented by a large number of connectors such as JDBC, 
Paimon, and Hive. Adding methods to it will greatly increase the implementation 
complexity, and more importantly, increase the cost of iteration, maintenance, 
and verification.

 

!image-2024-05-26-02-11-30-070.png|width=575,height=415!


> Introduce comment for CatalogStore & Support `ALTER CATALOG COMMENT` syntax
> ---
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Attachments: image-2024-06-13-18-01-34-910.png
>
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.
>  
> Set comment in the specified catalog. If the comment is already set in the 
> catalog, override the old value with the new one.
> !image-2024-06-13-18-01-34-910.png|width=715,height=523!



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

[jira] [Updated] (FLINK-34918) Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Description: 
We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
reasons are as follows.

1. For the sake of design consistency, follow the design of FLIP-295 [1] which 
introduced `CatalogStore` component, `CatalogDescriptor` includes names and 
attributes, both of which are used to describe the catalog, and `comment` can 
be added smoothly.

2. Extending the existing class rather than add new method to the existing 
interface, Especially, the `Catalog` interface, as a core interface, is used by 
a series of important components such as `CatalogFactory`, `CatalogManager` and 
`FactoryUtil`, and is implemented by a large number of connectors such as JDBC, 
Paimon, and Hive. Adding methods to it will greatly increase the implementation 
complexity, and more importantly, increase the cost of iteration, maintenance, 
and verification.

 

!image-2024-05-26-02-11-30-070.png|width=575,height=415!

  was:
We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
reasons are as follows.

1. For the sake of design consistency, follow the design of FLIP-295 [1] which 
introduced `CatalogStore` component, `CatalogDescriptor` includes names and 
attributes, both of which are used to describe the catalog, and `comment` can 
be added smoothly.

2. Extending the existing class rather than add new method to the existing 
interface, Especially, the `Catalog` interface, as a core interface, is used by 
a series of important components such as `CatalogFactory`, `CatalogManager` and 
`FactoryUtil`, and is implemented by a large number of connectors such as JDBC, 
Paimon, and Hive. Adding methods to it will greatly increase the implementation 
complexity, and more importantly, increase the cost of iteration, maintenance, 
and verification.


> Support `ALTER CATALOG COMMENT` syntax
> --
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.
>  
> !image-2024-05-26-02-11-30-070.png|width=575,height=415!



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

[jira] [Comment Edited] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li edited comment on FLINK-34914 at 6/13/24 11:49 AM:


[~Weijie Guo] Hi, sorry for the late reply. we are pushing the FLIP forward as 
soon as possible, and the most parts of works have been finished, so we could 
make it done in 1.20 :)


was (Author: liyubin117):
[~Weijie Guo] Hi, sorry for the late reply. we are pushing the FLIP forward as 
soon as possible, and most part of works have been finished, so we could make 
it done in 1.20 :)

> 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
>
> Umbrella issue for: 
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax



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

[jira] [Comment Edited] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li edited comment on FLINK-34914 at 6/13/24 11:43 AM:


[~Weijie Guo] Hi, sorry for the late reply. we are pushing the FLIP forward as 
soon as possible, and most part of works have been finished, so we could make 
it done in 1.20 :)


was (Author: liyubin117):
[~Weijie Guo] Hi, sorry for the late reply. we are pushing the FLIP forward as 
soon as possible, we have completed most part of works, so we could make it 
done in 1.20 :)

> 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
>
> Umbrella issue for: 
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax



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

[jira] [Commented] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

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

Yubin Li commented on FLINK-34914:
--

[~Weijie Guo] Hi, sorry for the late reply. we are pushing the FLIP forward as 
soon as possible, we have completed most part of works, so we could make it 
done in 1.20 :)

> 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
>
> Umbrella issue for: 
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax



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

[jira] [Updated] (FLINK-34918) Introduce comment for CatalogStore & Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Summary: Introduce comment for CatalogStore & Support `ALTER CATALOG 
COMMENT` syntax  (was: Support `ALTER CATALOG COMMENT` syntax)

> Introduce comment for CatalogStore & Support `ALTER CATALOG COMMENT` syntax
> ---
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.
>  
> !image-2024-05-26-02-11-30-070.png|width=575,height=415!



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

[jira] [Updated] (FLINK-34918) Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Summary: Support `ALTER CATALOG COMMENT` syntax  (was: Introduce comment 
for CatalogStore)

> Support `ALTER CATALOG COMMENT` syntax
> --
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.



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

[jira] [Updated] (FLINK-34918) Introduce comment for CatalogStore

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Summary: Introduce comment for CatalogStore  (was: Introduce comment for 
Catalog)

> Introduce comment for CatalogStore
> --
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.



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

[jira] [Created] (FLINK-35451) Support `ALTER CATALOG COMMENT` syntax

[Yubin Li (Jira)]

Yubin Li created FLINK-35451:


 Summary: Support `ALTER CATALOG COMMENT` syntax
 Key: FLINK-35451
 URL: https://issues.apache.org/jira/browse/FLINK-35451
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Reporter: Yubin Li
 Fix For: 1.20.0
 Attachments: image-2024-05-26-02-11-30-070.png

Set comment in the specified catalog. If the comment is already set in the 
catalog, override the old value with the new one.

!image-2024-05-26-02-11-30-070.png|width=575,height=415!



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

[jira] [Commented] (FLINK-35199) Support the execution of create materialized table in full refresh mode

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-35199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844652#comment-17844652
 ] 

Yubin Li commented on FLINK-35199:
--

[~lsy] Hi, This indeed is a valuable feature, Could I take this ?

> Support the execution of create materialized table in full refresh mode
> ---
>
> Key: FLINK-35199
> URL: https://issues.apache.org/jira/browse/FLINK-35199
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API, Table SQL / Gateway
>Affects Versions: 1.20.0
>Reporter: dalongliu
>Priority: Major
> Fix For: 1.20.0
>
>
> In full refresh mode, support creates materialized table and its background 
> refresh workflow:
> {code:SQL}
> CREATE MATERIALIZED TABLE [catalog_name.][db_name.]table_name
>  
> [ ([  ]) ]
>  
> [COMMENT table_comment]
>  
> [PARTITIONED BY (partition_column_name1, partition_column_name2, ...)]
>  
> [WITH (key1=val1, key2=val2, ...)]
>  
> FRESHNESS = INTERVAL '' { SECOND | MINUTE | HOUR | DAY }
>  
> [REFRESH_MODE = { CONTINUOUS | FULL }]
>  
> AS 
>  
> :
>   [CONSTRAINT constraint_name] PRIMARY KEY (column_name, ...) NOT ENFORCED
> {code}



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

[jira] [Commented] (FLINK-33379) Bump CI flink version on flink-connector-elasticsearch

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839184#comment-17839184
 ] 

Yubin Li commented on FLINK-33379:
--

[~pgodowski] sorry for the late reply, it seems that 3.1.0 branch not created 
yet, you could compile using master branch to support Flink 1.18

> Bump CI flink version on flink-connector-elasticsearch
> --
>
> Key: FLINK-33379
> URL: https://issues.apache.org/jira/browse/FLINK-33379
> Project: Flink
>  Issue Type: Improvement
>  Components: Connectors / ElasticSearch
>Affects Versions: elasticsearch-3.1.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Fix For: elasticsearch-3.1.0
>
> Attachments: image-2023-10-27-16-54-04-937.png
>
>
> As Flink 1.18 released, bump the flink version in es connector .



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

[jira] [Updated] (FLINK-34918) Introduce comment for Catalog

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Summary: Introduce comment for Catalog  (was: Introduce comment support for 
Catalog)

> Introduce comment for Catalog
> -
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.



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

[jira] [Created] (FLINK-35164) Support `ALTER CATALOG RESET` syntax

[Yubin Li (Jira)]

Yubin Li created FLINK-35164:


 Summary: Support `ALTER CATALOG RESET` syntax
 Key: FLINK-35164
 URL: https://issues.apache.org/jira/browse/FLINK-35164
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Reporter: Yubin Li
 Attachments: image-2024-04-18-23-26-59-854.png

h3. ALTER CATALOG catalog_name RESET (key1, key2, ...)

Reset one or more properties to its default value in the specified catalog.

!image-2024-04-18-23-26-59-854.png|width=781,height=527!



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

[jira] [Updated] (FLINK-34916) Support `ALTER CATALOG SET` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34916:
-
Summary: Support `ALTER CATALOG SET` syntax  (was: Support `ALTER CATALOG` 
syntax)

> Support `ALTER CATALOG SET` syntax
> --
>
> Key: FLINK-34916
> URL: https://issues.apache.org/jira/browse/FLINK-34916
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
> Attachments: image-2024-03-22-18-30-33-182.png
>
>
> Set one or more properties in the specified catalog. If a particular property 
> is already set in the catalog, override the old value with the new one.
> !image-2024-03-22-18-30-33-182.png|width=736,height=583!



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

[jira] [Updated] (FLINK-34915) Complete `DESCRIBE CATALOG` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34915:
-
 Attachment: image-2024-04-07-17-54-51-203.png
Description: 
Describe the metadata of an existing catalog. The metadata information includes 
the catalog’s name, type, and comment. If the optional {{EXTENDED}} option is 
specified, catalog properties are also returned.

NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and it 
is not actually available. we can complete the syntax in this FLIP. 

!image-2024-04-07-17-54-51-203.png|width=545,height=332!

  was:
Describe the metadata of an existing catalog. The metadata information includes 
the catalog’s name, type, and comment. If the optional {{EXTENDED}} option is 
specified, catalog properties are also returned.

NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and it 
is not actually available. we can complete the syntax in this FLIP. 

!image-2024-03-22-18-29-00-454.png|width=561,height=374!


> Complete `DESCRIBE CATALOG` syntax
> --
>
> Key: FLINK-34915
> URL: https://issues.apache.org/jira/browse/FLINK-34915
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Attachments: image-2024-03-22-18-29-00-454.png, 
> image-2024-04-07-17-54-51-203.png
>
>
> Describe the metadata of an existing catalog. The metadata information 
> includes the catalog’s name, type, and comment. If the optional {{EXTENDED}} 
> option is specified, catalog properties are also returned.
> NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and 
> it is not actually available. we can complete the syntax in this FLIP. 
> !image-2024-04-07-17-54-51-203.png|width=545,height=332!



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

[jira] [Updated] (FLINK-24939) Support 'SHOW CREATE CATALOG' syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-24939:
-
Summary: Support 'SHOW CREATE CATALOG' syntax  (was: Complete 'SHOW CREATE 
CATALOG' syntax)

> Support 'SHOW CREATE CATALOG' syntax
> 
>
> Key: FLINK-24939
> URL: https://issues.apache.org/jira/browse/FLINK-24939
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.14.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.20.0
>
>
> SHOW CREATE CATALOG ;
>  
> `Catalog` is playing a more import role in flink, it would be great to get 
> existing catalog detail information



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

[jira] [Updated] (FLINK-34915) Complete `DESCRIBE CATALOG` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34915:
-
Summary: Complete `DESCRIBE CATALOG` syntax  (was: Support `DESCRIBE 
CATALOG` syntax)

> Complete `DESCRIBE CATALOG` syntax
> --
>
> Key: FLINK-34915
> URL: https://issues.apache.org/jira/browse/FLINK-34915
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
> Attachments: image-2024-03-22-18-29-00-454.png
>
>
> Describe the metadata of an existing catalog. The metadata information 
> includes the catalog’s name, type, and comment. If the optional {{EXTENDED}} 
> option is specified, catalog properties are also returned.
> NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and 
> it is not actually available. we can complete the syntax in this FLIP. 
> !image-2024-03-22-18-29-00-454.png|width=561,height=374!



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

[jira] [Updated] (FLINK-24939) Complete 'SHOW CREATE CATALOG' syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-24939:
-
Summary: Complete 'SHOW CREATE CATALOG' syntax  (was: Support 'SHOW CREATE 
CATALOG' syntax)

> Complete 'SHOW CREATE CATALOG' syntax
> -
>
> Key: FLINK-24939
> URL: https://issues.apache.org/jira/browse/FLINK-24939
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.14.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.20.0
>
>
> SHOW CREATE CATALOG ;
>  
> `Catalog` is playing a more import role in flink, it would be great to get 
> existing catalog detail information



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

[jira] [Updated] (FLINK-34918) Introduce comment support for Catalog

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Summary: Introduce comment support for Catalog  (was: Introduce the support 
of Catalog for comments)

> Introduce comment support for Catalog
> -
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.



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

[jira] [Created] (FLINK-34918) Introduce the support of catalog for comments

[Yubin Li (Jira)]

Yubin Li created FLINK-34918:


 Summary: Introduce the support of catalog for comments
 Key: FLINK-34918
 URL: https://issues.apache.org/jira/browse/FLINK-34918
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Affects Versions: 1.20.0
Reporter: Yubin Li


We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
reasons are as follows.

1. For the sake of design consistency, follow the design of FLIP-295 [1] which 
introduced `CatalogStore` component, `CatalogDescriptor` includes names and 
attributes, both of which are used to describe the catalog, and `comment` can 
be added smoothly.

2. Extending the existing class rather than add new method to the existing 
interface, Especially, the `Catalog` interface, as a core interface, is used by 
a series of important components such as `CatalogFactory`, `CatalogManager` and 
`FactoryUtil`, and is implemented by a large number of connectors such as JDBC, 
Paimon, and Hive. Adding methods to it will greatly increase the implementation 
complexity, and more importantly, increase the cost of iteration, maintenance, 
and verification.



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

[jira] [Updated] (FLINK-34918) Introduce the support of Catalog for comments

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34918:
-
Summary: Introduce the support of Catalog for comments  (was: Introduce the 
support of catalog for comments)

> Introduce the support of Catalog for comments
> -
>
> Key: FLINK-34918
> URL: https://issues.apache.org/jira/browse/FLINK-34918
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
>
> We propose to introduce `getComment()` method in `CatalogDescriptor`, and the 
> reasons are as follows.
> 1. For the sake of design consistency, follow the design of FLIP-295 [1] 
> which introduced `CatalogStore` component, `CatalogDescriptor` includes names 
> and attributes, both of which are used to describe the catalog, and `comment` 
> can be added smoothly.
> 2. Extending the existing class rather than add new method to the existing 
> interface, Especially, the `Catalog` interface, as a core interface, is used 
> by a series of important components such as `CatalogFactory`, 
> `CatalogManager` and `FactoryUtil`, and is implemented by a large number of 
> connectors such as JDBC, Paimon, and Hive. Adding methods to it will greatly 
> increase the implementation complexity, and more importantly, increase the 
> cost of iteration, maintenance, and verification.



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

[jira] [Created] (FLINK-34917) Support enhanced `CREATE CATALOG` syntax

[Yubin Li (Jira)]

Yubin Li created FLINK-34917:


 Summary: Support enhanced `CREATE CATALOG` syntax
 Key: FLINK-34917
 URL: https://issues.apache.org/jira/browse/FLINK-34917
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Affects Versions: 1.20.0
Reporter: Yubin Li
 Attachments: image-2024-03-22-18-31-59-632.png

{{IF NOT EXISTS}}  clause: If the catalog already exists, nothing happens.

{{COMMENT}} clause: An optional string literal. The description for the catalog.

NOTICE: we just need to introduce the '[IF NOT EXISTS]' and '[COMMENT]' clause 
to the 'create catalog' statement.

!image-2024-03-22-18-31-59-632.png|width=795,height=87!



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

[jira] [Created] (FLINK-34916) Support `ALTER CATALOG` syntax

[Yubin Li (Jira)]

Yubin Li created FLINK-34916:


 Summary: Support `ALTER CATALOG` syntax
 Key: FLINK-34916
 URL: https://issues.apache.org/jira/browse/FLINK-34916
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Affects Versions: 1.20.0
Reporter: Yubin Li
 Attachments: image-2024-03-22-18-30-33-182.png

Set one or more properties in the specified catalog. If a particular property 
is already set in the catalog, override the old value with the new one.

!image-2024-03-22-18-30-33-182.png|width=736,height=583!



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

[jira] [Created] (FLINK-34915) Introduce `DESCRIBE CATALOG` syntax

[Yubin Li (Jira)]

Yubin Li created FLINK-34915:


 Summary: Introduce `DESCRIBE CATALOG` syntax
 Key: FLINK-34915
 URL: https://issues.apache.org/jira/browse/FLINK-34915
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Affects Versions: 1.20.0
Reporter: Yubin Li


Describe the metadata of an existing catalog. The metadata information includes 
the catalog’s name, type, and comment. If the optional {{EXTENDED}} option is 
specified, catalog properties are also returned.

NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and it 
is not actually available. we can complete the syntax in this FLIP. 
{{Flink SQL> describe catalog cat2;}}
{{+--+---+}}
{{| catalog_description_item | catalog_description_value |}}
{{+--+---+}}
{{| Name |  cat2 |}}
{{| Type | generic_in_memory |}}
{{|  Comment |   |}}
{{+--+---+}}
{{3 rows }}{{in}} {{set}}
 
{{Flink SQL> describe catalog extended cat2;}}
{{+--+-+}}
{{| catalog_description_item |   catalog_description_value 
|}}
{{+--+-+}}
{{| Name |    cat2 
|}}
{{| Type |   generic_in_memory 
|}}
{{|  Comment | 
|}}
{{{}|   Properties | (default-database,db), 
({}}}{{{}type{}}}{{{},generic_in_memory) |{}}}
{{+--+-+}}
{{4 rows }}{{in}} {{set}}



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

[jira] [Updated] (FLINK-34915) Support `DESCRIBE CATALOG` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34915:
-
Description: 
Describe the metadata of an existing catalog. The metadata information includes 
the catalog’s name, type, and comment. If the optional {{EXTENDED}} option is 
specified, catalog properties are also returned.

NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and it 
is not actually available. we can complete the syntax in this FLIP. 

!image-2024-03-22-18-29-00-454.png|width=561,height=374!

  was:
Describe the metadata of an existing catalog. The metadata information includes 
the catalog’s name, type, and comment. If the optional {{EXTENDED}} option is 
specified, catalog properties are also returned.

NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and it 
is not actually available. we can complete the syntax in this FLIP. 
{{Flink SQL> describe catalog cat2;}}
{{+--+---+}}
{{| catalog_description_item | catalog_description_value |}}
{{+--+---+}}
{{| Name |  cat2 |}}
{{| Type | generic_in_memory |}}
{{|  Comment |   |}}
{{+--+---+}}
{{3 rows }}{{in}} {{set}}
 
{{Flink SQL> describe catalog extended cat2;}}
{{+--+-+}}
{{| catalog_description_item |   catalog_description_value 
|}}
{{+--+-+}}
{{| Name |    cat2 
|}}
{{| Type |   generic_in_memory 
|}}
{{|  Comment | 
|}}
{{{}|   Properties | (default-database,db), 
({}}}{{{}type{}}}{{{},generic_in_memory) |{}}}
{{+--+-+}}
{{4 rows }}{{in}} {{set}}


> Support `DESCRIBE CATALOG` syntax
> -
>
> Key: FLINK-34915
> URL: https://issues.apache.org/jira/browse/FLINK-34915
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-03-22-18-29-00-454.png
>
>
> Describe the metadata of an existing catalog. The metadata information 
> includes the catalog’s name, type, and comment. If the optional {{EXTENDED}} 
> option is specified, catalog properties are also returned.
> NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and 
> it is not actually available. we can complete the syntax in this FLIP. 
> !image-2024-03-22-18-29-00-454.png|width=561,height=374!



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

[jira] [Updated] (FLINK-34915) Support `DESCRIBE CATALOG` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34915:
-
Attachment: image-2024-03-22-18-29-00-454.png

> Support `DESCRIBE CATALOG` syntax
> -
>
> Key: FLINK-34915
> URL: https://issues.apache.org/jira/browse/FLINK-34915
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-03-22-18-29-00-454.png
>
>
> Describe the metadata of an existing catalog. The metadata information 
> includes the catalog’s name, type, and comment. If the optional {{EXTENDED}} 
> option is specified, catalog properties are also returned.
> NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and 
> it is not actually available. we can complete the syntax in this FLIP. 
> {{Flink SQL> describe catalog cat2;}}
> {{+--+---+}}
> {{| catalog_description_item | catalog_description_value |}}
> {{+--+---+}}
> {{| Name |  cat2 |}}
> {{| Type | generic_in_memory |}}
> {{|  Comment |   |}}
> {{+--+---+}}
> {{3 rows }}{{in}} {{set}}
>  
> {{Flink SQL> describe catalog extended cat2;}}
> {{+--+-+}}
> {{| catalog_description_item |   
> catalog_description_value |}}
> {{+--+-+}}
> {{| Name |    
> cat2 |}}
> {{| Type |   
> generic_in_memory |}}
> {{|  Comment |
>  |}}
> {{{}|   Properties | (default-database,db), 
> ({}}}{{{}type{}}}{{{},generic_in_memory) |{}}}
> {{+--+-+}}
> {{4 rows }}{{in}} {{set}}



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

[jira] [Updated] (FLINK-34915) Support `DESCRIBE CATALOG` syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34915:
-
Summary: Support `DESCRIBE CATALOG` syntax  (was: Introduce `DESCRIBE 
CATALOG` syntax)

> Support `DESCRIBE CATALOG` syntax
> -
>
> Key: FLINK-34915
> URL: https://issues.apache.org/jira/browse/FLINK-34915
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.20.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2024-03-22-18-29-00-454.png
>
>
> Describe the metadata of an existing catalog. The metadata information 
> includes the catalog’s name, type, and comment. If the optional {{EXTENDED}} 
> option is specified, catalog properties are also returned.
> NOTICE: The parser part of this syntax has been implemented in FLIP-69 , and 
> it is not actually available. we can complete the syntax in this FLIP. 
> {{Flink SQL> describe catalog cat2;}}
> {{+--+---+}}
> {{| catalog_description_item | catalog_description_value |}}
> {{+--+---+}}
> {{| Name |  cat2 |}}
> {{| Type | generic_in_memory |}}
> {{|  Comment |   |}}
> {{+--+---+}}
> {{3 rows }}{{in}} {{set}}
>  
> {{Flink SQL> describe catalog extended cat2;}}
> {{+--+-+}}
> {{| catalog_description_item |   
> catalog_description_value |}}
> {{+--+-+}}
> {{| Name |    
> cat2 |}}
> {{| Type |   
> generic_in_memory |}}
> {{|  Comment |
>  |}}
> {{{}|   Properties | (default-database,db), 
> ({}}}{{{}type{}}}{{{},generic_in_memory) |{}}}
> {{+--+-+}}
> {{4 rows }}{{in}} {{set}}



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

[jira] [Updated] (FLINK-24939) Support 'SHOW CREATE CATALOG' syntax

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-24939:
-
Parent: FLINK-34914
Issue Type: Sub-task  (was: Improvement)

> Support 'SHOW CREATE CATALOG' syntax
> 
>
> Key: FLINK-24939
> URL: https://issues.apache.org/jira/browse/FLINK-24939
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.14.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>
> SHOW CREATE CATALOG ;
>  
> `Catalog` is playing a more import role in flink, it would be great to get 
> existing catalog detail information



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

[jira] [Created] (FLINK-34914) FLIP-436: Introduce Catalog-related Syntax

[Yubin Li (Jira)]

Yubin Li created FLINK-34914:


 Summary: 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


Umbrella issue for: 
https://cwiki.apache.org/confluence/display/FLINK/FLIP-436%3A+Introduce+Catalog-related+Syntax



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

[jira] [Commented] (FLINK-34898) Cannot create named STRUCT with a single field

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-34898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829371#comment-17829371
 ] 

Yubin Li commented on FLINK-34898:
--

I use the latest version to run the syntax and work fine, maybe you could try 
1.19.

!image-2024-03-21-12-00-00-183.png|width=688,height=161!

> Cannot create named STRUCT with a single field
> --
>
> Key: FLINK-34898
> URL: https://issues.apache.org/jira/browse/FLINK-34898
> Project: Flink
>  Issue Type: Bug
>Reporter: Chloe He
>Priority: Major
> Attachments: image-2024-03-21-12-00-00-183.png
>
>
> I'm trying to create named structs using Flink SQL and I found a previous 
> ticket https://issues.apache.org/jira/browse/FLINK-9161 that mentions the use 
> of the following syntax:
> {code:java}
> SELECT CAST(('a', 1) as ROW) AS row1;
> {code}
> However, my named struct has a single field and effectively it should look 
> something like `\{"a": 1}`. I can't seem to be able to find a way to 
> construct this. I have experimented with a few different syntax and it either 
> throws parsing error or casting error:
> {code:java}
> Cast function cannot convert value of type INTEGER to type 
> RecordType(VARCHAR(2147483647) a) {code}



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

[jira] [Updated] (FLINK-34898) Cannot create named STRUCT with a single field

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34898:
-
Attachment: image-2024-03-21-12-00-00-183.png

> Cannot create named STRUCT with a single field
> --
>
> Key: FLINK-34898
> URL: https://issues.apache.org/jira/browse/FLINK-34898
> Project: Flink
>  Issue Type: Bug
>Reporter: Chloe He
>Priority: Major
> Attachments: image-2024-03-21-12-00-00-183.png
>
>
> I'm trying to create named structs using Flink SQL and I found a previous 
> ticket https://issues.apache.org/jira/browse/FLINK-9161 that mentions the use 
> of the following syntax:
> {code:java}
> SELECT CAST(('a', 1) as ROW) AS row1;
> {code}
> However, my named struct has a single field and effectively it should look 
> something like `\{"a": 1}`. I can't seem to be able to find a way to 
> construct this. I have experimented with a few different syntax and it either 
> throws parsing error or casting error:
> {code:java}
> Cast function cannot convert value of type INTEGER to type 
> RecordType(VARCHAR(2147483647) a) {code}



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

[jira] [Commented] (FLINK-34351) Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-34351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820968#comment-17820968
 ] 

Yubin Li commented on FLINK-34351:
--

[~lincoln.86xy] There is no problem about the test :)

> Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs 
> using SQL Hint
> ---
>
> Key: FLINK-34351
> URL: https://issues.apache.org/jira/browse/FLINK-34351
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Jane Chan
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.19.0
>
> Attachments: image-2024-02-21-15-24-22-289.png, 
> image-2024-02-21-15-24-43-212.png
>
>
> This describes how to verify FLINK-33397: Support Configuring Different State 
> TTLs using SQL Hint.
>  
> The verification steps are as follows.
> 1. Start the standalone session cluster and sql client.
> 2. Execute the following DDL statements.
> {code:sql}
> CREATE TABLE `default_catalog`.`default_database`.`Orders` (
>   `order_id` INT,
>   `line_order_id` INT
> ) WITH (
>   'connector' = 'datagen', 
>   'rows-per-second' = '5'
> ); 
> CREATE TABLE `default_catalog`.`default_database`.`LineOrders` (
>   `line_order_id` INT,
>   `ship_mode` STRING
> ) WITH (
>   'connector' = 'datagen',
>   'rows-per-second' = '5'
> );
> CREATE TABLE `default_catalog`.`default_database`.`OrdersShipInfo` (
>   `order_id` INT,
>   `line_order_id` INT,
>   `ship_mode` STRING ) WITH (
>   'connector' = 'print'
> ); {code}
> 3. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to join
> {code:sql}
> -- SET the pipeline level state TTL to 24h
> SET 'table.exec.state.ttl' = '24h';
> -- Configure different state TTL for join operator
> COMPILE PLAN '/path/to/join-plan.json' FOR
> INSERT INTO OrdersShipInfo 
> SELECT /*+STATE_TTL('a' = '2d', 'b' = '12h')*/ a.order_id, a.line_order_id, 
> b.ship_mode 
> FROM Orders a JOIN LineOrders b ON a.line_order_id = b.line_order_id;
> {code}
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamJoin ExecNode.
> {code:json}
> {
> "id" : 5,
> "type" : "stream-exec-join_1",
> "joinSpec" : {
>   ...
> },
> "state" : [ {
>   "index" : 0,
>   "ttl" : "2 d",
>   "name" : "leftState"
> }, {
>   "index" : 1,
>   "ttl" : "12 h",
>   "name" : "rightState"
> } ],
> "inputProperties": [...],
> "outputType": ...,
> "description": ...
> }
> {code}
> 4. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to group aggregate
> {code:sql}
> CREARE TABLE source_t (
> a INT,
> b BIGINT,
> c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> CREARE TABLE sink_t (
> b BIGINT PRIMARY KEY NOT ENFORCED,
> cnt BIGINT,
> avg_a DOUBLE,
> min_c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> COMPILE PLAN '/path/to/agg-plan.json' FOR
> INSERT INTO sink_t SELECT /*+ STATE_TTL('source_t' = '1s') */
> b, 
> COUNT(*) AS cnt,
> AVG(a) FILTER (WHERE a > 1) AS avg_a
> MIN(c) AS min_c 
> FROM source_t GROUP BY b
> {code}
>  
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamExecGroupAggregate ExecNode.
> {code:json}
> "state" : [ {
>   "index" : 0,
>   "ttl" : "1 s",
>   "name" : "groupAggregateState"
> } ]
> {code}



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

[jira] [Commented] (FLINK-34351) Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-34351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819104#comment-17819104
 ] 

Yubin Li commented on FLINK-34351:
--

[~qingyue] I found some typos in the original test scripts, stage 4 should be 
as follows:
{code:java}
CREATE TABLE source_t (
a INT,
b BIGINT,
c STRING
) WITH (
'connector' = 'datagen',
'rows-per-second' = '5'
);

CREATE TABLE sink_t (
b BIGINT PRIMARY KEY NOT ENFORCED,
cnt BIGINT,
avg_a DOUBLE,
min_c STRING
) WITH (
'connector' = 'print'
);
COMPILE PLAN '/path/to/agg-plan.json' FOR
INSERT INTO sink_t SELECT /*+ STATE_TTL('source_t' = '1s') */
b, 
COUNT(*) AS cnt,
AVG(a) FILTER (WHERE a > 1) AS avg_a,
MIN(c) AS min_c 
FROM source_t GROUP BY b;{code}
After careful tests, the practical feature takes effect actually.

!image-2024-02-21-15-24-43-212.png|width=294,height=197!

!image-2024-02-21-15-24-22-289.png|width=418,height=127!

> Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs 
> using SQL Hint
> ---
>
> Key: FLINK-34351
> URL: https://issues.apache.org/jira/browse/FLINK-34351
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Jane Chan
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.19.0
>
> Attachments: image-2024-02-21-15-24-22-289.png, 
> image-2024-02-21-15-24-43-212.png
>
>




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

[jira] [Updated] (FLINK-34351) Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34351:
-
Attachment: image-2024-02-21-15-24-22-289.png

> Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs 
> using SQL Hint
> ---
>
> Key: FLINK-34351
> URL: https://issues.apache.org/jira/browse/FLINK-34351
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Jane Chan
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.19.0
>
> Attachments: image-2024-02-21-15-24-22-289.png, 
> image-2024-02-21-15-24-43-212.png
>
>




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

[jira] [Updated] (FLINK-34351) Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-34351:
-
Attachment: image-2024-02-21-15-24-43-212.png

> Release Testing: Verify FLINK-33397 Support Configuring Different State TTLs 
> using SQL Hint
> ---
>
> Key: FLINK-34351
> URL: https://issues.apache.org/jira/browse/FLINK-34351
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Jane Chan
>Assignee: Yubin Li
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.19.0
>
> Attachments: image-2024-02-21-15-24-22-289.png, 
> image-2024-02-21-15-24-43-212.png
>
>




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

[jira] [Commented] (FLINK-34298) Release Testing Instructions: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819038#comment-17819038
 ] 

Yubin Li commented on FLINK-34298:
--

[~qingyue] Thanks for your detailed instructions

> Release Testing Instructions: Verify FLINK-33397 Support Configuring 
> Different State TTLs using SQL Hint
> 
>
> Key: FLINK-34298
> URL: https://issues.apache.org/jira/browse/FLINK-34298
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: lincoln lee
>Assignee: Jane Chan
>Priority: Blocker
> Fix For: 1.19.0
>
>
> This ticket describes how to verify FLINK-33397: Support Configuring 
> Different State TTLs using SQL Hint.
>  
> The verification steps are as follows.
> 1. Start the standalone session cluster and sql client.
> 2. Execute the following DDL statements.
> {code:sql}
> CREATE TABLE `default_catalog`.`default_database`.`Orders` (
>   `order_id` INT,
>   `line_order_id` INT
> ) WITH (
>   'connector' = 'datagen', 
>   'rows-per-second' = '5'
> ); 
> CREATE TABLE `default_catalog`.`default_database`.`LineOrders` (
>   `line_order_id` INT,
>   `ship_mode` STRING
> ) WITH (
>   'connector' = 'datagen',
>   'rows-per-second' = '5'
> );
> CREATE TABLE `default_catalog`.`default_database`.`OrdersShipInfo` (
>   `order_id` INT,
>   `line_order_id` INT,
>   `ship_mode` STRING ) WITH (
>   'connector' = 'print'
> ); {code}
> 3. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to join
> {code:sql}
> -- SET the pipeline level state TTL to 24h
> SET 'table.exec.state.ttl' = '24h';
> -- Configure different state TTL for join operator
> COMPILE PLAN '/path/to/join-plan.json' FOR
> INSERT INTO OrdersShipInfo 
> SELECT /*+STATE_TTL('a' = '2d', 'b' = '12h')*/ a.order_id, a.line_order_id, 
> b.ship_mode 
> FROM Orders a JOIN LineOrders b ON a.line_order_id = b.line_order_id;
> {code}
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamJoin ExecNode.
> {code:json}
> {
> "id" : 5,
> "type" : "stream-exec-join_1",
> "joinSpec" : {
>   ...
> },
> "state" : [ {
>   "index" : 0,
>   "ttl" : "2 d",
>   "name" : "leftState"
> }, {
>   "index" : 1,
>   "ttl" : "12 h",
>   "name" : "rightState"
> } ],
> "inputProperties": [...],
> "outputType": ...,
> "description": ...
> }
> {code}
> 4. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to group aggregate
> {code:sql}
> CREARE TABLE source_t (
> a INT,
> b BIGINT,
> c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> CREARE TABLE sink_t (
> b BIGINT PRIMARY KEY NOT ENFORCED,
> cnt BIGINT,
> avg_a DOUBLE,
> min_c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> COMPILE PLAN '/path/to/agg-plan.json' FOR
> INSERT INTO sink_t SELECT /*+ STATE_TTL('source_t' = '1s') */
> b, 
> COUNT(*) AS cnt,
> AVG(a) FILTER (WHERE a > 1) AS avg_a
> MIN(c) AS min_c 
> FROM source_t GROUP BY b
> {code}
>  
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamExecGroupAggregate ExecNode.
> {code:json}
> "state" : [ {
>   "index" : 0,
>   "ttl" : "1 s",
>   "name" : "groupAggregateState"
> } ]
> {code}



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

[jira] (FLINK-34298) Release Testing Instructions: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

[ https://issues.apache.org/jira/browse/FLINK-34298 ]


Yubin Li deleted comment on FLINK-34298:
--

was (Author: liyubin117):
[~qingyue] Thanks, I will finish the tests as soon as possible.

> Release Testing Instructions: Verify FLINK-33397 Support Configuring 
> Different State TTLs using SQL Hint
> 
>
> Key: FLINK-34298
> URL: https://issues.apache.org/jira/browse/FLINK-34298
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: lincoln lee
>Assignee: Jane Chan
>Priority: Blocker
> Fix For: 1.19.0
>
>
> This ticket describes how to verify FLINK-33397: Support Configuring 
> Different State TTLs using SQL Hint.
>  
> The verification steps are as follows.
> 1. Start the standalone session cluster and sql client.
> 2. Execute the following DDL statements.
> {code:sql}
> CREATE TABLE `default_catalog`.`default_database`.`Orders` (
>   `order_id` INT,
>   `line_order_id` INT
> ) WITH (
>   'connector' = 'datagen', 
>   'rows-per-second' = '5'
> ); 
> CREATE TABLE `default_catalog`.`default_database`.`LineOrders` (
>   `line_order_id` INT,
>   `ship_mode` STRING
> ) WITH (
>   'connector' = 'datagen',
>   'rows-per-second' = '5'
> );
> CREATE TABLE `default_catalog`.`default_database`.`OrdersShipInfo` (
>   `order_id` INT,
>   `line_order_id` INT,
>   `ship_mode` STRING ) WITH (
>   'connector' = 'print'
> ); {code}
> 3. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to join
> {code:sql}
> -- SET the pipeline level state TTL to 24h
> SET 'table.exec.state.ttl' = '24h';
> -- Configure different state TTL for join operator
> COMPILE PLAN '/path/to/join-plan.json' FOR
> INSERT INTO OrdersShipInfo 
> SELECT /*+STATE_TTL('a' = '2d', 'b' = '12h')*/ a.order_id, a.line_order_id, 
> b.ship_mode 
> FROM Orders a JOIN LineOrders b ON a.line_order_id = b.line_order_id;
> {code}
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamJoin ExecNode.
> {code:json}
> {
> "id" : 5,
> "type" : "stream-exec-join_1",
> "joinSpec" : {
>   ...
> },
> "state" : [ {
>   "index" : 0,
>   "ttl" : "2 d",
>   "name" : "leftState"
> }, {
>   "index" : 1,
>   "ttl" : "12 h",
>   "name" : "rightState"
> } ],
> "inputProperties": [...],
> "outputType": ...,
> "description": ...
> }
> {code}
> 4. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to group aggregate
> {code:sql}
> CREARE TABLE source_t (
> a INT,
> b BIGINT,
> c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> CREARE TABLE sink_t (
> b BIGINT PRIMARY KEY NOT ENFORCED,
> cnt BIGINT,
> avg_a DOUBLE,
> min_c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> COMPILE PLAN '/path/to/agg-plan.json' FOR
> INSERT INTO sink_t SELECT /*+ STATE_TTL('source_t' = '1s') */
> b, 
> COUNT(*) AS cnt,
> AVG(a) FILTER (WHERE a > 1) AS avg_a
> MIN(c) AS min_c 
> FROM source_t GROUP BY b
> {code}
>  
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamExecGroupAggregate ExecNode.
> {code:json}
> "state" : [ {
>   "index" : 0,
>   "ttl" : "1 s",
>   "name" : "groupAggregateState"
> } ]
> {code}



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

[jira] [Commented] (FLINK-34298) Release Testing Instructions: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819037#comment-17819037
 ] 

Yubin Li commented on FLINK-34298:
--

[~qingyue] Thanks, I will finish the tests as soon as possible.

> Release Testing Instructions: Verify FLINK-33397 Support Configuring 
> Different State TTLs using SQL Hint
> 
>
> Key: FLINK-34298
> URL: https://issues.apache.org/jira/browse/FLINK-34298
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: lincoln lee
>Assignee: Jane Chan
>Priority: Blocker
> Fix For: 1.19.0
>
>
> This ticket describes how to verify FLINK-33397: Support Configuring 
> Different State TTLs using SQL Hint.
>  
> The verification steps are as follows.
> 1. Start the standalone session cluster and sql client.
> 2. Execute the following DDL statements.
> {code:sql}
> CREATE TABLE `default_catalog`.`default_database`.`Orders` (
>   `order_id` INT,
>   `line_order_id` INT
> ) WITH (
>   'connector' = 'datagen', 
>   'rows-per-second' = '5'
> ); 
> CREATE TABLE `default_catalog`.`default_database`.`LineOrders` (
>   `line_order_id` INT,
>   `ship_mode` STRING
> ) WITH (
>   'connector' = 'datagen',
>   'rows-per-second' = '5'
> );
> CREATE TABLE `default_catalog`.`default_database`.`OrdersShipInfo` (
>   `order_id` INT,
>   `line_order_id` INT,
>   `ship_mode` STRING ) WITH (
>   'connector' = 'print'
> ); {code}
> 3. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to join
> {code:sql}
> -- SET the pipeline level state TTL to 24h
> SET 'table.exec.state.ttl' = '24h';
> -- Configure different state TTL for join operator
> COMPILE PLAN '/path/to/join-plan.json' FOR
> INSERT INTO OrdersShipInfo 
> SELECT /*+STATE_TTL('a' = '2d', 'b' = '12h')*/ a.order_id, a.line_order_id, 
> b.ship_mode 
> FROM Orders a JOIN LineOrders b ON a.line_order_id = b.line_order_id;
> {code}
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamJoin ExecNode.
> {code:json}
> {
> "id" : 5,
> "type" : "stream-exec-join_1",
> "joinSpec" : {
>   ...
> },
> "state" : [ {
>   "index" : 0,
>   "ttl" : "2 d",
>   "name" : "leftState"
> }, {
>   "index" : 1,
>   "ttl" : "12 h",
>   "name" : "rightState"
> } ],
> "inputProperties": [...],
> "outputType": ...,
> "description": ...
> }
> {code}
> 4. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to group aggregate
> {code:sql}
> CREARE TABLE source_t (
> a INT,
> b BIGINT,
> c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> CREARE TABLE sink_t (
> b BIGINT PRIMARY KEY NOT ENFORCED,
> cnt BIGINT,
> avg_a DOUBLE,
> min_c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> COMPILE PLAN '/path/to/agg-plan.json' FOR
> INSERT INTO sink_t SELECT /*+ STATE_TTL('source_t' = '1s') */
> b, 
> COUNT(*) AS cnt,
> AVG(a) FILTER (WHERE a > 1) AS avg_a
> MIN(c) AS min_c 
> FROM source_t GROUP BY b
> {code}
>  
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamExecGroupAggregate ExecNode.
> {code:json}
> "state" : [ {
>   "index" : 0,
>   "ttl" : "1 s",
>   "name" : "groupAggregateState"
> } ]
> {code}



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

[jira] [Commented] (FLINK-34298) Release Testing Instructions: Verify FLINK-33397 Support Configuring Different State TTLs using SQL Hint

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-34298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814022#comment-17814022
 ] 

Yubin Li commented on FLINK-34298:
--

[~qingyue] I would like to take this, please assign this to me, thanks!

> Release Testing Instructions: Verify FLINK-33397 Support Configuring 
> Different State TTLs using SQL Hint
> 
>
> Key: FLINK-34298
> URL: https://issues.apache.org/jira/browse/FLINK-34298
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: lincoln lee
>Priority: Blocker
>  Labels: release-testing
> Fix For: 1.19.0
>
>
> This ticket aims to verify FLINK-33397: Support Configuring Different State 
> TTLs using SQL Hint.
>  
> The verification steps are as follows.
> 1. Start the standalone session cluster and sql client.
> 2. Execute the following DDL statements.
> {code:sql}
> CREATE TABLE `default_catalog`.`default_database`.`Orders` (
>   `order_id` INT,
>   `line_order_id` INT
> ) WITH (
>   'connector' = 'datagen', 
>   'rows-per-second' = '5'
> ); 
> CREATE TABLE `default_catalog`.`default_database`.`LineOrders` (
>   `line_order_id` INT,
>   `ship_mode` STRING
> ) WITH (
>   'connector' = 'datagen',
>   'rows-per-second' = '5'
> );
> CREATE TABLE `default_catalog`.`default_database`.`OrdersShipInfo` (
>   `order_id` INT,
>   `line_order_id` INT,
>   `ship_mode` STRING ) WITH (
>   'connector' = 'print'
> ); {code}
> 3. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to join
> {code:sql}
> -- SET the pipeline level state TTL to 24h
> SET 'table.exec.state.ttl' = '24h';
> -- Configure different state TTL for join operator
> COMPILE PLAN '/path/to/join-plan.json' FOR
> INSERT INTO OrdersShipInfo 
> SELECT /*+STATE_TTL('a' = '2d', 'b' = '12h')*/ a.order_id, a.line_order_id, 
> b.ship_mode 
> FROM Orders a JOIN LineOrders b ON a.line_order_id = b.line_order_id;
> {code}
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamJoin ExecNode.
> {code:json}
> {
> "id" : 5,
> "type" : "stream-exec-join_1",
> "joinSpec" : {
>   ...
> },
> "state" : [ {
>   "index" : 0,
>   "ttl" : "2 d",
>   "name" : "leftState"
> }, {
>   "index" : 1,
>   "ttl" : "12 h",
>   "name" : "rightState"
> } ],
> "inputProperties": [...],
> "outputType": ...,
> "description": ...
> }
> {code}
> 4. Compile and verify the INSERT INTO statement with the STATE_TTL hint 
> applied to group aggregate
> {code:sql}
> CREARE TABLE source_t (
> a INT,
> b BIGINT,
> c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> CREARE TABLE sink_t (
> b BIGINT PRIMARY KEY NOT ENFORCED,
> cnt BIGINT,
> avg_a DOUBLE,
> min_c STRING
> ) WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '5'
> );
> COMPILE PLAN '/path/to/agg-plan.json' FOR
> INSERT INTO sink_t SELECT /*+ STATE_TTL('source_t' = '1s') */
> b, 
> COUNT(*) AS cnt,
> AVG(a) FILTER (WHERE a > 1) AS avg_a
> MIN(c) AS min_c 
> FROM source_t GROUP BY b
> {code}
>  
> The generated JSON file *should* contain the following "state" JSON array for 
> StreamExecGroupAggregate ExecNode.
> {code:json}
> "state" : [ {
>   "index" : 0,
>   "ttl" : "1 s",
>   "name" : "groupAggregateState"
> } ]
> {code}



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

[jira] [Commented] (FLINK-33927) Cleanup usage of deprecated ExecutionConfigOptions#(TABLE_EXEC_SHUFFLE_MODE, TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS)

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800308#comment-17800308
 ] 

Yubin Li commented on FLINK-33927:
--

[~qingyue] Looking forward your review :)

> Cleanup usage of deprecated ExecutionConfigOptions#(TABLE_EXEC_SHUFFLE_MODE, 
> TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS)
> ---
>
> Key: FLINK-33927
> URL: https://issues.apache.org/jira/browse/FLINK-33927
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / Planner
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>  Labels: pull-request-available
>
> |org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_SHUFFLE_MODE|
> |org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS|



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

[jira] [Updated] (FLINK-33927) Cleanup usage of deprecated ExecutionConfigOptions#(TABLE_EXEC_SHUFFLE_MODE, TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS)

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-33927:
-
Description: 
|org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_SHUFFLE_MODE|
|org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS|

  was:
|org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_SHUFFLE_MODE|Use
 ExecutionOptions#BATCH_SHUFFLE_MODE instead|
|org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS|Use
 #TABLE_EXEC_UID_GENERATION instead|


> Cleanup usage of deprecated ExecutionConfigOptions#(TABLE_EXEC_SHUFFLE_MODE, 
> TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS)
> ---
>
> Key: FLINK-33927
> URL: https://issues.apache.org/jira/browse/FLINK-33927
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / Planner
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>
> |org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_SHUFFLE_MODE|
> |org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS|



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

[jira] [Created] (FLINK-33927) Cleanup usage of deprecated ExecutionConfigOptions#(TABLE_EXEC_SHUFFLE_MODE, TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS)

[Yubin Li (Jira)]

Yubin Li created FLINK-33927:


 Summary: Cleanup usage of deprecated 
ExecutionConfigOptions#(TABLE_EXEC_SHUFFLE_MODE, 
TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS)
 Key: FLINK-33927
 URL: https://issues.apache.org/jira/browse/FLINK-33927
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / Planner
Affects Versions: 1.19.0
Reporter: Yubin Li


|org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_SHUFFLE_MODE|Use
 ExecutionOptions#BATCH_SHUFFLE_MODE instead|
|org.apache.flink.table.api.config.ExecutionConfigOptions#TABLE_EXEC_LEGACY_TRANSFORMATION_UIDS|Use
 #TABLE_EXEC_UID_GENERATION instead|



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

[jira] [Updated] (FLINK-33921) Cleanup usage of deprecated IdleStateRetentionTime related method in org.apache.flink.table.api.TableConfig

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-33921:
-
Description: 
getMinIdleStateRetentionTime()
getMaxIdleStateRetentionTime()

  was:
getMinIdleStateRetentionTime()
getMinIdleStateRetentionTime()


> Cleanup usage of deprecated IdleStateRetentionTime related method in 
> org.apache.flink.table.api.TableConfig
> ---
>
> Key: FLINK-33921
> URL: https://issues.apache.org/jira/browse/FLINK-33921
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / Planner
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>
> getMinIdleStateRetentionTime()
> getMaxIdleStateRetentionTime()



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

[jira] [Commented] (FLINK-33921) Cleanup usage of deprecated IdleStateRetentionTime related method in org.apache.flink.table.api.TableConfig

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799328#comment-17799328
 ] 

Yubin Li commented on FLINK-33921:
--

[~qingyue] Could you please assign this to me? thanks!

> Cleanup usage of deprecated IdleStateRetentionTime related method in 
> org.apache.flink.table.api.TableConfig
> ---
>
> Key: FLINK-33921
> URL: https://issues.apache.org/jira/browse/FLINK-33921
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / Planner
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>
> getMinIdleStateRetentionTime()
> getMinIdleStateRetentionTime()



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

[jira] [Updated] (FLINK-33921) Cleanup usage of deprecated IdleStateRetentionTime related method in org.apache.flink.table.api.TableConfig

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-33921:
-
Parent: FLINK-31596
Issue Type: Sub-task  (was: Improvement)

> Cleanup usage of deprecated IdleStateRetentionTime related method in 
> org.apache.flink.table.api.TableConfig
> ---
>
> Key: FLINK-33921
> URL: https://issues.apache.org/jira/browse/FLINK-33921
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / Planner
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>
> getMinIdleStateRetentionTime()
> getMinIdleStateRetentionTime()



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

[jira] [Created] (FLINK-33921) Cleanup usage of deprecated IdleStateRetentionTime related method in org.apache.flink.table.api.TableConfig

[Yubin Li (Jira)]

Yubin Li created FLINK-33921:


 Summary: Cleanup usage of deprecated IdleStateRetentionTime 
related method in org.apache.flink.table.api.TableConfig
 Key: FLINK-33921
 URL: https://issues.apache.org/jira/browse/FLINK-33921
 Project: Flink
  Issue Type: Improvement
  Components: Table SQL / Planner
Affects Versions: 1.19.0
Reporter: Yubin Li


getMinIdleStateRetentionTime()
getMinIdleStateRetentionTime()



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

[jira] [Commented] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795648#comment-17795648
 ] 

Yubin Li commented on FLINK-33780:
--

[~hackergin] [~Leonard]  Thanks for your review :D

It maybe more appropriate to initialize the default catalog when calling 
`Builder.defaultCatalog` rather than when building `CatalogManager`, but 
introducing a new method in `CatalogManger.Builder` requires changing all 
related calls.

If we adopt the solution, there is only one minor comment that 
`CatalogDescriptor` has already included `catalogName`, so it may be more 
appropriate to use `defaultCatalog(CatalogDescriptor catalogDescriptor)`. WDYT?

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png, 
> image-2023-12-11-14-14-10-002.png, image-2023-12-12-11-09-53-075.png, 
> image-2023-12-12-13-42-04-762.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795574#comment-17795574
 ] 

Yubin Li edited comment on FLINK-33780 at 12/12/23 5:42 AM:


[~hackergin] Hi, we could make modifitions in the `CatalogManager` construct 
function as follows:

!image-2023-12-12-11-09-53-075.png|width=798,height=406!

DefaultCatalog is the current catalog of a session including SqlGateway, 
`default_catalog` is like `d2` under the context `use catalog d2`, the only 
difference is that it is created implicitly by Flink, we should treat them 
equally for semantic consistency, WDYT?

!image-2023-12-12-13-42-04-762.png|width=422,height=184!


was (Author: liyubin117):
[~hackergin] Hi, we could make modifitions in the `CatalogManager` construct 
function as follows:

!image-2023-12-12-11-09-53-075.png|width=1165,height=593!

DefaultCatalog is the current catalog of a session including SqlGateway, 
`default_catalog` is like `d2` under the context `use catalog d2`, the only 
difference is that it is created implicitly by Flink, we should treat them 
equally for semantic consistency, WDYT?

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png, 
> image-2023-12-11-14-14-10-002.png, image-2023-12-12-11-09-53-075.png, 
> image-2023-12-12-13-42-04-762.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795574#comment-17795574
 ] 

Yubin Li edited comment on FLINK-33780 at 12/12/23 3:22 AM:


[~hackergin] Hi, we could make modifitions in the `CatalogManager` construct 
function as follows:

!image-2023-12-12-11-09-53-075.png|width=1165,height=593!

DefaultCatalog is the current catalog of a session including SqlGateway, 
`default_catalog` is like `d2` under the context `use catalog d2`, the only 
difference is that it is created implicitly by Flink, we should treat them 
equally for semantic consistency, WDYT?


was (Author: liyubin117):
[~hackergin] Hi, we could make modifitions in the `CatalogManager` construct 
function as follows:

!image-2023-12-12-11-09-53-075.png|width=1165,height=593!

DefaultCatalog is the current catalog of a session including SqlGateway, 
`default_catalog` is like `d2` under the context `use catalog d2`, only the 
difference is that it is created implicitly by Flink, we should treat them 
equally for semantic consistency, WDYT?

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png, 
> image-2023-12-11-14-14-10-002.png, image-2023-12-12-11-09-53-075.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795574#comment-17795574
 ] 

Yubin Li edited comment on FLINK-33780 at 12/12/23 3:21 AM:


[~hackergin] Hi, we could make modifitions in the `CatalogManager` construct 
function as follows:

!image-2023-12-12-11-09-53-075.png|width=1165,height=593!

DefaultCatalog is the current catalog of a session including SqlGateway, 
`default_catalog` is like `d2` under the context `use catalog d2`, only the 
difference is that it is created implicitly by Flink, we should treat them 
equally for semantic consistency, WDYT?


was (Author: liyubin117):
[~hackergin] Hi, we could make modifitions in the `CatalogManager` construct 
function as follows:

!image-2023-12-12-11-09-53-075.png|width=1165,height=593!

DefaultCatalog is the current catalog of a session including SqlGateway, 
`default_catalog` is like `d2`, only the difference is that it is created 
implicitly by Flink, we should treat them equally for semantic consistency, 
WDYT?

!image-2023-12-11-14-14-10-002.png|width=805,height=565!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png, 
> image-2023-12-11-14-14-10-002.png, image-2023-12-12-11-09-53-075.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Commented] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795574#comment-17795574
 ] 

Yubin Li commented on FLINK-33780:
--

[~hackergin] Hi, we could make modifitions in the `CatalogManager` construct 
function as follows:

!image-2023-12-12-11-09-53-075.png|width=1165,height=593!

DefaultCatalog is the current catalog of a session including SqlGateway, 
`default_catalog` is like `d2`, only the difference is that it is created 
implicitly by Flink, we should treat them equally for semantic consistency, 
WDYT?

!image-2023-12-11-14-14-10-002.png|width=805,height=565!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png, 
> image-2023-12-11-14-14-10-002.png, image-2023-12-12-11-09-53-075.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Updated] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-33780:
-
Attachment: image-2023-12-12-11-09-53-075.png

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png, 
> image-2023-12-11-14-14-10-002.png, image-2023-12-12-11-09-53-075.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795171#comment-17795171
 ] 

Yubin Li edited comment on FLINK-33780 at 12/11/23 6:14 AM:


[~hackergin] Thanks for your attention:)

In addition to the conceptual necessity (default catalog is also part of 
catalogs equaly and not differ from others), I also found that the `show create 
catalog` statement  proposed in 
https://issues.apache.org/jira/browse/FLINK-24939 would expose the absence of 
the default catalog in the CatalogStore, I have implemented the statement on 
our production env using `CatalogStore`.

!image-2023-12-11-14-14-10-002.png|width=821,height=576!


was (Author: liyubin117):
[~hackergin] Thanks for your attention:)

In addition to the conceptual necessity (default catalog is also part of 
catalogs equaly and not differ from others), I also found that the `show create 
catalog` statement  proposed in 
https://issues.apache.org/jira/browse/FLINK-24939 would expose the absence of 
the default catalog in the CatalogStore, I have implemented the statement on 
our production env using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png, 
> image-2023-12-11-14-14-10-002.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795171#comment-17795171
 ] 

Yubin Li edited comment on FLINK-33780 at 12/11/23 6:13 AM:


[~hackergin] Thanks for your attention:)

In addition to the conceptual necessity (default catalog is also part of 
catalogs equaly and not differ from others), I also found that the `show create 
catalog` statement  proposed in 
https://issues.apache.org/jira/browse/FLINK-24939 would expose the absence of 
the default catalog in the CatalogStore, I have implemented the statement on 
our production env using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!


was (Author: liyubin117):
[~hackergin] Thanks for your attention:)

In addition to the conceptual necessity (default catalog is also part of 
catalogs), I also found that the `show create catalog` statement  proposed in 
https://issues.apache.org/jira/browse/FLINK-24939 would expose the absence of 
the default catalog in the CatalogStore, I have implemented the statement on 
our production env using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795171#comment-17795171
 ] 

Yubin Li edited comment on FLINK-33780 at 12/11/23 5:53 AM:


[~hackergin] Thanks for your attention:)

In addition to the conceptual necessity (default catalog is also part of 
catalogs), I also found that the `show create catalog` statement  proposed in 
https://issues.apache.org/jira/browse/FLINK-24939 would expose the absence of 
the default catalog in the CatalogStore, I have implemented the statement on 
our production env using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!


was (Author: liyubin117):
[~hackergin] In addition to the conceptual necessity (default catalog is also 
part of catalogs), I also found that the `show create catalog` statement  
proposed in https://issues.apache.org/jira/browse/FLINK-24939 would expose the 
absence of the default catalog in the CatalogStore, I have implemented the 
statement on our production env using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795171#comment-17795171
 ] 

Yubin Li edited comment on FLINK-33780 at 12/11/23 5:52 AM:


[~hackergin] In addition to the conceptual necessity (default catalog is also 
part of catalogs), I also found that the `show create catalog` statement  
proposed in https://issues.apache.org/jira/browse/FLINK-24939 would expose the 
absence of the default catalog in the CatalogStore, I have implemented the 
statement on our production env using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!


was (Author: liyubin117):
[~hackergin] In addition to the conceptual necessity (default catalog is also 
part of catalogs), I also found that the `show create catalog` statement  
proposed in https://issues.apache.org/jira/browse/FLINK-24939 would expose the 
absence of the default catalog in the CatalogStore, I have implemented the 
statement on our production dev using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795171#comment-17795171
 ] 

Yubin Li edited comment on FLINK-33780 at 12/11/23 5:51 AM:


[~hackergin] In addition to the conceptual necessity (default catalog is also 
part of catalogs), I also found that the `show create catalog` statement  
proposed in https://issues.apache.org/jira/browse/FLINK-24939 would expose the 
absence of the default catalog in the CatalogStore, I have implemented the 
statement on our production dev using `CatalogStore`.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!


was (Author: liyubin117):
[~hackergin] In addition to the conceptual necessity (default catalog is also 
part of catalogs), I also found that the `show create catalog` statement  
proposed in https://issues.apache.org/jira/browse/FLINK-24939 would expose the 
absence of the default catalog in the CatalogStore.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Commented] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795171#comment-17795171
 ] 

Yubin Li commented on FLINK-33780:
--

[~hackergin] In addition to the conceptual necessity (default catalog is also 
part of catalogs), I also found that the `show create catalog` statement  
proposed in https://issues.apache.org/jira/browse/FLINK-24939 would expose the 
absence of the default catalog in the CatalogStore.

!image-2023-12-11-13-47-29-623.png|width=702,height=290!

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Updated] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-33780:
-
Attachment: image-2023-12-11-13-47-29-623.png

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
> Attachments: image-2023-12-11-13-47-29-623.png
>
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Comment Edited] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794581#comment-17794581
 ] 

Yubin Li edited comment on FLINK-33780 at 12/8/23 9:58 AM:
---

[~hackergin] Hi, looking forward to your suggestions :) I have implemented 
this, and if the feature is neccessary, could you please assign this to me? 
thanks~


was (Author: liyubin117):
[~hackergin] Hi, looking forward to your suggestions :) I have implemented 
this, and if it is neccessary, could you please assign this to me? thanks~

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Commented] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794581#comment-17794581
 ] 

Yubin Li commented on FLINK-33780:
--

[~hackergin] Hi, looking forward to your suggestions :) I have implemented 
this, and if it is neccessary, could you please assign this to me? thanks~

> Support to store default catalog in CatalogStore
> 
>
> Key: FLINK-33780
> URL: https://issues.apache.org/jira/browse/FLINK-33780
> Project: Flink
>  Issue Type: Sub-task
>  Components: Table SQL / API
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>
> Flink initially creates a default catalog which is included in the 
> `Map catalogs`, but is not stored in the CatalogStore.
> After conducting thorough investigation, I've determined that the necessary 
> modification can be made within the `CatalogManager`.



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

[jira] [Created] (FLINK-33780) Support to store default catalog in CatalogStore

[Yubin Li (Jira)]

Yubin Li created FLINK-33780:


 Summary: Support to store default catalog in CatalogStore
 Key: FLINK-33780
 URL: https://issues.apache.org/jira/browse/FLINK-33780
 Project: Flink
  Issue Type: Sub-task
  Components: Table SQL / API
Affects Versions: 1.19.0
Reporter: Yubin Li


Flink initially creates a default catalog which is included in the `Map catalogs`, but is not stored in the CatalogStore.

After conducting thorough investigation, I've determined that the necessary 
modification can be made within the `CatalogManager`.



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

[jira] [Commented] (FLINK-33638) Support variable-length data generation for variable-length data types

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790860#comment-17790860
 ] 

Yubin Li commented on FLINK-33638:
--

[~lincoln] I have finished the feature according to 
https://issues.apache.org/jira/browse/FLINK-25284

now CI has passed, PTAL, thanks :D 

> Support variable-length data generation for variable-length data types
> --
>
> Key: FLINK-33638
> URL: https://issues.apache.org/jira/browse/FLINK-33638
> Project: Flink
>  Issue Type: Improvement
>  Components: Connectors / Common
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>  Labels: pull-request-available
>
> Currently, for variable-length data types (varchar, varbinary, string, 
> bytes), datagen connector always generates max-length data, we can extending 
> datagen to generate variable length values(using a new option to enable it, 
> e.g.,'fields.f0.var-len'='true').
> the topic has been discussed in the mail thread 
> [https://lists.apache.org/thread/kp6popo4cnhl6vx31sdn6mlscpzj9tgc]



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

[jira] [Commented] (FLINK-33638) Support variable-length data generation for variable-length data types

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789889#comment-17789889
 ] 

Yubin Li commented on FLINK-33638:
--

[~lincoln] thanks very much!

> Support variable-length data generation for variable-length data types
> --
>
> Key: FLINK-33638
> URL: https://issues.apache.org/jira/browse/FLINK-33638
> Project: Flink
>  Issue Type: Improvement
>  Components: Connectors / Common
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Assignee: Yubin Li
>Priority: Major
>
> Currently, for variable-length data types (varchar, varbinary, string, 
> bytes), datagen connector always generates max-length data, we can extending 
> datagen to generate variable length values(using a new option to enable it, 
> e.g.,'fields.f0.var-len'='true').
> the topic has been discussed in the mail thread 
> [https://lists.apache.org/thread/kp6popo4cnhl6vx31sdn6mlscpzj9tgc]



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

[jira] [Commented] (FLINK-33638) Support variable-length data generation for variable-length data types

[Yubin Li (Jira)]

[ 
https://issues.apache.org/jira/browse/FLINK-33638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789425#comment-17789425
 ] 

Yubin Li commented on FLINK-33638:
--

[~lincoln] Hi, could you please assign this to me? thanks!

> Support variable-length data generation for variable-length data types
> --
>
> Key: FLINK-33638
> URL: https://issues.apache.org/jira/browse/FLINK-33638
> Project: Flink
>  Issue Type: Improvement
>  Components: Connectors / Common
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>
> Currently, for variable-length data types (varchar, varbinary, string, 
> bytes), datagen connector always generates max-length data, we can extending 
> datagen to generate variable length values(using a new option to enable it, 
> e.g.,'fields.f0.var-len'='true').
> the topic has been discussed in the mail thread 
> [https://lists.apache.org/thread/kp6popo4cnhl6vx31sdn6mlscpzj9tgc]



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

[jira] [Created] (FLINK-33638) Support variable-length data generation for variable-length data types

[Yubin Li (Jira)]

Yubin Li created FLINK-33638:


 Summary: Support variable-length data generation for 
variable-length data types
 Key: FLINK-33638
 URL: https://issues.apache.org/jira/browse/FLINK-33638
 Project: Flink
  Issue Type: Improvement
  Components: Connectors / Common
Affects Versions: 1.19.0
Reporter: Yubin Li


Currently, for variable-length data types (varchar, varbinary, string, bytes), 
datagen connector always generates max-length data, we can extending datagen to 
generate variable length values(using a new option to enable it, 
e.g.,'fields.f0.var-len'='true').

the topic has been discussed in the mail thread 
[https://lists.apache.org/thread/kp6popo4cnhl6vx31sdn6mlscpzj9tgc]



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

[jira] [Updated] (FLINK-32993) Datagen connector handles length-constrained fields according to the schema definition by default

[Yubin Li (Jira)]

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

Yubin Li updated FLINK-32993:
-
Summary: Datagen connector handles length-constrained fields according to 
the schema definition by default  (was: Datagen connector handles data types 
according to the schema definition by default)

> Datagen connector handles length-constrained fields according to the schema 
> definition by default
> -
>
> Key: FLINK-32993
> URL: https://issues.apache.org/jira/browse/FLINK-32993
> Project: Flink
>  Issue Type: Improvement
>  Components: Connectors / Common
>Affects Versions: 1.19.0
>Reporter: Yubin Li
>Priority: Major
>  Labels: pull-request-available
> Attachments: image-2023-08-30-11-47-05-887.png, 
> image-2023-08-30-11-47-43-719.png, image-2023-08-30-11-51-44-498.png, 
> image-2023-08-30-13-44-10-106.png, image-2023-08-30-13-56-12-468.png, 
> image-2023-08-30-13-56-28-403.png
>
>
> create table as follows:
> !image-2023-08-30-11-51-44-498.png!
> results:
> !image-2023-08-30-11-47-05-887.png!
> I have found that Char type data length is 100 instead of defined 50.
> we could help users to deal with the following data types in a proper way, 
> thus allow the datagen connector to automatically generate data that conforms 
> to the schema definition without additional manual configuration.
>  # fixed-length data types (char, binary) , the length should be defined by 
> schema definion, and could not be user-defined length.
>  # variable-length data types (varchar, varbinary), the length should be 
> defined by schema definition, and could be the user-defined length which less 
> than schema definition.



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