You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "kcheng.mvp (JIRA)" <ji...@apache.org> on 2016/04/07 10:36:25 UTC

[jira] [Issue Comment Deleted] (IGNITE-1481) It is possible to configure local cache with affinity function

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

kcheng.mvp updated IGNITE-1481:
-------------------------------
    Comment: was deleted

(was: I checked the latest code, seems some did the fix. if so can we close this jira?)

> It is possible to configure local cache with affinity function
> --------------------------------------------------------------
>
>                 Key: IGNITE-1481
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1481
>             Project: Ignite
>          Issue Type: Bug
>          Components: newbie
>            Reporter: Andrey Gura
>            Assignee: kcheng.mvp
>              Labels: newbie
>
> {{LOCAL}} cache always uses {{GridCacheProcessor.LocalAffinityFunction}}.
> Durign configuration of local cache it is possible to pass other affinity function to cache configuration. All cache operations will work correctly, but user can obtain affinity manager that internally uses incorrect affinity function ({{GridCacheContext.cctx.affinity().aff.aff}}).
> Expected behaviour: {{GridCacheContext.cctx.affinity().aff.aff}} always refers to {{GridCacheProcessor.LocalAffinityFunction}} for {{LOCAL}} caches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)