You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2021/09/16 21:40:00 UTC

[jira] [Created] (IGNITE-15532) Tuple equality comparison.

Andrey Mashenkov created IGNITE-15532:
-----------------------------------------

             Summary: Tuple equality comparison.
                 Key: IGNITE-15532
                 URL: https://issues.apache.org/jira/browse/IGNITE-15532
             Project: Ignite
          Issue Type: Improvement
            Reporter: Andrey Mashenkov
             Fix For: 3.0.0-alpha3


For now. Tuple implementations don't overrides 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 fields 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)