ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-691) CacheObjectContext always contains default affinity mapper
Date Wed, 08 Apr 2015 13:43:13 GMT

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

Vladimir Ozerov commented on IGNITE-691:

I do not understand semantics of this method. What is going on here? 
What means null-node and configuration? 
What means node with null-configuration?

The latter method is called from DataStreamerImpl.<init> and GridAffinityProcessor.affinityInfoFromNode().

> CacheObjectContext always contains default affinity mapper
> ----------------------------------------------------------
>                 Key: IGNITE-691
>                 URL: https://issues.apache.org/jira/browse/IGNITE-691
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: sprint-2
>            Reporter: Valentin Kulichenko
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: sprint-3
> When {{CacheObjectContext}} is created (see {{IgniteacheObjectProcessorImpl.contextForCache()}}
method, default affinity mapper is also created regardless whether there is a custom mapper
in configuration or not. This looks suspicious, so need to create a test for custom affinity
mapper and fix if needed.

This message was sent by Atlassian JIRA

View raw message