[IGNITE-20155] Java client connector skips NOT NULL and other column checks

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0
• Component/s: thin client
• Labels: ignite-3
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 03/Aug/23 15:08
• Updated: 04/Sep/24 16:10
• Resolved: 24/Aug/23 09:01

Description

See TupleMarshallerImpl#marshal and #binaryTupleRebuildRequired: we pass BinaryTuple as is from the client, bypassing NOT NULL and other constraint checks.

We should validate the data from the client without reassembling the tuple.

Issue Links

• Discovered while testing: IGNITE-19835 Java thin 3.0: Reject POJOs with unmapped fields
• is caused by: IGNITE-18925 Thin 3.0: Avoid BinaryTuple conversion from client to storage
• links to: GitHub Pull Request #2491