ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Tikhonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4551) Reconsider cache key/value peer class loading
Date Wed, 15 Mar 2017 17:19:41 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926587#comment-15926587
] 

Nikolay Tikhonov commented on IGNITE-4551:
------------------------------------------

As possible solution we can propagate {{KeyClassloaderId}} and {{ValueClassLoaderId}} to {{DataRow}},
similar did for {{expireTime}}.

> Reconsider cache key/value peer class loading
> ---------------------------------------------
>
>                 Key: IGNITE-4551
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4551
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Alexey Goncharuk
>            Assignee: Nikolay Tikhonov
>             Fix For: 2.0
>
>
> In new cache implementation after entry is written in offheap information about key/value
classloaders in lost (before classloader ids were stored in swap/offheap see GridCacheMapEntry.swap
in 'master').
> Need decide how it should work with new architecture (maybe single type per cache can
simplify implementation).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message