Vladimir Ozerov created IGNITE-2722:
---------------------------------------
Summary: Inconsistent "keepBinary" flag propagation for
EVT_CACHE_REBALANCE_OBJECT_LOADED event.
Key: IGNITE-2722
URL: https://issues.apache.org/jira/browse/IGNITE-2722
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Priority: Critical
Fix For: 1.6
I searched through usages of EVT_CACHE_REBALANCE_OBJECT_LOADED event and
noticed that we pass different value of "keepBinary" flag in different
situations:
1) {{GridDhtLockFuture.MiniFuture.onResult}} - false
2) {{GridDhtTxPrepareFuture.MiniFuture.onResult}} - false
2) {{GridDhtForceKeysFuture.MiniFuture.onResult}} - false
4) {{GridDhtPartitionDemander.preloadEntry}} - true
Looks like with this approach user is not able to use corresponding event
listener normally because he will receive both serialized and de-serialized
objects.
As I understand, we must always pass {{true}} here because we do not know
whether node has corresponding classes or not.
Other rebalance events must be reviewed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
