[IGNITE-15532] Tuple equality comparison.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha3
• Labels: iep-54 ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Andrey Mashenkov
• Reporter: Andrey Mashenkov
• Created: 16/Sep/21 21:39
• Updated: 22/Sep/21 10:39
• Resolved: 22/Sep/21 10:39

Description

For now. Tuple implementations don't override hashcode/equals methods.
This makes them non-comparable with each other and limits Tuple usage in Set/Map collections.
But we already use Tuple in that way (see KVBinaryView API).

Let's

• Make all key columns mandatory, otherwise it is impossible to match missed key columns and columns with a default value.
• Specify requirements to hashcode in method javadoc. Hashcode must be independent of columns order (uses XOR operation).
• Make external equals/hashcode implementation as a static method of some util class to reuse it in all Tuple out implementations.

Issue Links

• links to: GitHub Pull Request #346