You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/04/14 11:11:42 UTC
[jira] [Comment Edited] (IGNITE-4983) .NET: Cache plugins do not
work
[ https://issues.apache.org/jira/browse/IGNITE-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968896#comment-15968896 ]
Pavel Tupitsyn edited comment on IGNITE-4983 at 4/14/17 11:11 AM:
------------------------------------------------------------------
We should probably remove {{ICachePluginProvider}} and related infrastructure and leave only Java-based plugins in place ({{ICachePluginConfiguration}} with non-null {{CachePluginConfigurationClosureFactoryId}}), since current infrastructure on .NET side does not play along with new Java aprt at all.
was (Author: ptupitsyn):
We should probably remove {{ICachePluginProvider}} and related infrastructure and leave only Java-based plugins in place ({{ICachePluginConfiguration}} with non-null {{CachePluginConfigurationClosureFactoryId}}).
> .NET: Cache plugins do not work
> -------------------------------
>
> Key: IGNITE-4983
> URL: https://issues.apache.org/jira/browse/IGNITE-4983
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.0
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 2.0
>
>
> IGNITE-3477 brought breaking changes to cache plugin infrastructure. Now cache plugins can not exist independently of grid plugins: {{PluginProvider.createCacheProvider}} creates cache provider, instead of {{CachePluginConfiguration.createProvider}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)