Aitozi created FLINK-24624:
--
Summary: Add clean up phase when kubernetes session start failed
Key: FLINK-24624
URL: https://issues.apache.org/jira/browse/FLINK-24624
Project: Flink
Issue Type: Impro
Aitozi created FLINK-24625:
--
Summary: Expose the required kubernetes permission from the shell
command
Key: FLINK-24625
URL: https://issues.apache.org/jira/browse/FLINK-24625
Project: Flink
Issue T
Kenyore created FLINK-24626:
---
Summary: Flink JDBC Sink may lose data in retract stream
Key: FLINK-24626
URL: https://issues.apache.org/jira/browse/FLINK-24626
Project: Flink
Issue Type: Bug
Hi Ingo,
I thought again.
I'll try to sort out the current catalog behaviors.
Actually, we can divide catalogs into three categories:
1. ExternalCatalog: it can only read or create a single table kind
which connects to external storage. TableFactory is provided by
Catalog, which can have nothing
Hang Ruan created FLINK-24627:
-
Summary: Add some generic junit5 extensions to replace junit4 rules
Key: FLINK-24627
URL: https://issues.apache.org/jira/browse/FLINK-24627
Project: Flink
Issue Ty
Hi Jingsong,
thanks again for the answers. I think requiring catalogs to implement an
interface to support BDTs is something we'll need (though personally I
still prefer explicit DDL here over the "no connector option" approach).
What about more edge cases like
CREATE TABLE T (f0 INT);
ALTER TAB
