[BugFix] Resolve Delete Semantics Data Loss in Flink SQL for StarRocks 3.1 #365
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.
In the 3.1 storage-computation separated version, using the INSERT INTO statement in Flink SQL will lose data with Delete semantics.
What type of PR is this:
Which issues of this PR fixes :
Fixes #364
Problem Summary(Required) :
In the storage-computation separated version, the primary key information is not stored in the information_schema.COLUMNS table, causing the Flink connector to fail to detect the primary key and assume that the StarRocks table does not support writing Flink delete rowkind data.
Solution: Determine whether to support delete semantics based on the primary key declaration in the Flink table.
Checklist: