[Feature] TableWrite skip null fields check, when RowKind is DELETE
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Motivation
When deleting a row from PrimaryKey Table, we can set the RowKind type to RowKind.DELETE.
Currently, the TableWriteImpl class will always invoke checkNullability method, ensure all fileds comply with null constraint,
We suggest only verify primary keys null constraint if RowKind is DELETE, then when delete a row, only need provide primary keys.
### Solution
_No response_
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating TableWriteImpl and its checkNullability call, then trace how RowKind.DELETE records are written and how primary-key tables enforce null constraints. Confirm the change by checking that delete rows require only non-null primary keys while non-delete rows still validate all fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100