You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually, the data will be completed even though only pk provided. And since deletion is rare comparing to insert and update, ignoring other field check wont save too much time.
Actually, the data will be completed even though only pk provided. And since deletion is rare comparing to insert and update, ignoring other field check wont save too much time.
He is not trying to save time, he can only provide the primary key field and no other fields, in order to avoid errors
Search before asking
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?
The text was updated successfully, but these errors were encountered: