[flink] Add regression test and docs for nested NOT NULL constraints - #4198
Open
leekeiabstraction wants to merge 2 commits into
Open
[flink] Add regression test and docs for nested NOT NULL constraints#4198leekeiabstraction wants to merge 2 commits into
leekeiabstraction wants to merge 2 commits into
Conversation
leekeiabstraction
force-pushed
the
nested-not-null-regression-test
branch
from
September 2, 2026 07:15
355dbd0 to
4255113
Compare
Flink before 2.2 drops nested NOT NULL constraints during DDL resolution (FLINK-20539), so this adds a Flink 2.2/2.3 catalog ITCase for the Fluss round trip and documents the limitation for older Flink versions.
leekeiabstraction
force-pushed
the
nested-not-null-regression-test
branch
from
September 2, 2026 07:18
4255113 to
eb9b056
Compare
Contributor
Author
|
@gyang94 Appreciate a review here |
Contributor
|
@leekeiabstraction cool, It is a bug in Flink side. It is enough for us to aware of it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linked issue: close #4062
Flink before 2.2 drops nested
NOT NULLconstraints during DDL resolution (FLINK-20539), before the Fluss catalog receives the schema, so nothing can be recovered on the Fluss side for older versions. This addstestCreateTableWithNestedNotNullto the Flink 2.2/2.3 catalog ITCases to guard the Fluss round trip and documents the limitation in the Flink DDL page, including theNOT NULLworkaround forROW,ARRAYandMAPon older versions.Fluss does not enforce nested
NOT NULLon write and Flink'stable.exec.sink.nested-constraint-enforcerdefaults toIGNORE, so a null in a nestedNOT NULLfield is written and fails every subsequent read of that record. The docs recommendROWS_AND_COLLECTIONS; write-time validation in Fluss is left for a follow-up.