[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4551: Fix Version/s: (was: 2.4) > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.5 > > > 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 (v7.6.3#76005)
[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4551: Fix Version/s: 2.5 > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.5 > > > 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 (v7.6.3#76005)
[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-4551: - Fix Version/s: (was: 2.3) 2.4 > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.4 > > > 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.4.14#64029)
[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-4551: --- Labels: MakeTeamcityGreenAgain Muted_test (was: MakeTeamcityGreenAgain) > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Assignee: Nikolay Tikhonov > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.2 > > > 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.4.14#64029)
[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev updated IGNITE-4551: -- Labels: MakeTeamcityGreenAgain (was: ) > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Assignee: Nikolay Tikhonov > Labels: MakeTeamcityGreenAgain > Fix For: 2.2 > > > 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.4.14#64029)
[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4551: Fix Version/s: (was: 2.1) 2.2 > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk > Fix For: 2.2 > > > 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.4.14#64029)
[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4551: Fix Version/s: (was: 2.0) 2.1 > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Assignee: Nikolay Tikhonov > Fix For: 2.1 > > > 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)
[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-4551: - Issue Type: Bug (was: Sub-task) Parent: (was: IGNITE-3477) > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > 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)
