[
https://issues.apache.org/jira/browse/IGNITE-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131473#comment-15131473
]
kcheng.mvp commented on IGNITE-1481:
------------------------------------
No breaks, and the new added unit test passed as well.
http://204.14.53.151/viewLog.html?currentGroup=test&scope=org.apache.ignite.testsuites.IgniteCacheTestSuite%23teamcity%23org.apache.ignite.cache.affinity.local%23teamcity%23LocalAffinityFunctionTest&pager.currentPage=1&order=DURATION_DESC&recordsPerPage=500&filterText=local&status=&buildTypeId=bt150&buildId=107788&tab=testsInfo
> 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
>
> {{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)
