[
https://issues.apache.org/jira/browse/IGNITE-9702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Cherkasov updated IGNITE-9702:
--------------------------------------
Description:
Right now:
BinObjectImpl(a=1,b=2) != BinObjectImpl(b=2,a=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.
was:
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.
> 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
> Assignee: Mikhail Cherkasov
> Priority: Blocker
> Fix For: 3.0
>
>
> Right now:
> BinObjectImpl(a=1,b=2) != BinObjectImpl(b=2,a=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)
