ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-2722) Inconsistent "keepBinary" flag propagation for EVT_CACHE_REBALANCE_OBJECT_LOADED event.
Date Thu, 25 Aug 2016 06:45:20 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Semen Boikov updated IGNITE-2722:
---------------------------------
    Assignee:     (was: Semen Boikov)

> 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
>             Fix For: 1.8
>
>
> 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)

Mime
View raw message