[IGNITE-21793] Fix inconsistencies in table view APIs

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0
• Fix Version/s: 3.1
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Pavel Tupitsyn
• Reporter: Alexey Scherbakov
• Created: 19/Mar/24 08:30
• Updated: 25/Sep/24 13:57

Description

1. getOrDefault accepts nullables after IGNITE-20524, but its semantics is to ensure null safety. It should not accept or nulls (getNullable methods exist to deal with nulls)
2. getNullable family of methods throws exceptions from tuple-based views (ClientKeyValueBinaryView, KeyValueBinaryViewImpl), but it should work same as equivalent getters to ensure view equivalence. (fixed in IGNITE-23003)
3. getAndReplaceAsync has nullable key and value, but actual implementations (client and embedded) disallow nulls.
4. getNullableAndPut throws MarshallerException when value is null, unlike getAndPut which correctly throws NullPointerException

Issue Links

• is caused by: IGNITE-20524 Inconsistent behavior of KeyValueView.put with null value
• is related to: IGNITE-23164 ClientKeyValueBinaryView.get() operation returns tuple with key column
• relates to: IGNITE-23003 KeyValueBinaryView::getNullable should not throw UnsupportedOperation exception
• relates to: IGNITE-16707 Unify table API integration tests