Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
At the moment the PostgresCatalog does not create field constraints (at the moment there's only UNIQUE and PRIMARY_KEY in the TableSchema..could it worth to add also NOT_NULL?)
We only pass primary key to catalog table for now. UNIQUE and NOT NULL information will be future work.
Attachments
Issue Links
- fixes
-
FLINK-17762 Postgres Catalog should pass table's primary key to catalogTable
- Closed
- links to