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

Posted to dev@ignite.apache.org by "Mikhail Cherkasov (JIRA)" <ji...@apache.org> on 2018/09/26 13:58:00 UTC

[jira] [Created] (IGNITE-9702) Make IGNITE_BINARY_SORT_OBJECT_FIELDS enabled by default

Mikhail Cherkasov created IGNITE-9702:
-----------------------------------------

             Summary: Make IGNITE_BINARY_SORT_OBJECT_FIELDS enabled by default
                 Key: IGNITE-9702
                 URL: https://issues.apache.org/jira/browse/IGNITE-9702
             Project: Ignite
          Issue Type: Bug
            Reporter: Mikhail Cherkasov
             Fix For: 3.0


Right now:

BinObjectImpl(a=1,b=2) != BinObjectImpl(a=2,b=1), so hash code of binary object depends of fields order and for ignite it's too different objects.

It's unclear and counter-intuitive for a user.

However, this can not be changed till 3.0, because it breaks compatibility with existent storage and requites migration with downtime and an util that will migrate binary objects to a new internal fields order.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)