[jira] [Commented] (IGNITE-4457) Define cache plugin API in .NET

2017-01-20 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn commented on IGNITE-4457:


{{CachePluginContext}} refactored, {{OnIgniteStop}} callback added, tests 
improved, merged with {{ignite-2.0}}.

> Define cache plugin API in .NET
> ---
>
> Key: IGNITE-4457
> URL: https://issues.apache.org/jira/browse/IGNITE-4457
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Define cache plugin API in .NET similar to Java API:
> * {{CacheConfiguration.PluginConfigurations}}
> * {{ICachePluginProvider}}
> * {{ICachePluginContext}}
> Fundamental difference to Ignite plugins (IGNITE-4441), which are local, is 
> that {{CachePluginConfiguration}} is sent to remote nodes and providers are 
> created there. So we'll need {{PlatformCachePluginConfiguration}} and 
> {{PlatformCachePluginProvider}} on Java side.



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

[jira] [Commented] (IGNITE-4457) Define cache plugin API in .NET

2017-01-19 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn commented on IGNITE-4457:


Let's make CachePluginContext generic to be consistent with IGNITE-4441

> Define cache plugin API in .NET
> ---
>
> Key: IGNITE-4457
> URL: https://issues.apache.org/jira/browse/IGNITE-4457
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
>  Labels: .NET
> Fix For: 2.0
>
>
> Define cache plugin API in .NET similar to Java API:
> * {{CacheConfiguration.PluginConfigurations}}
> * {{ICachePluginProvider}}
> * {{ICachePluginContext}}
> Fundamental difference to Ignite plugins (IGNITE-4441), which are local, is 
> that {{CachePluginConfiguration}} is sent to remote nodes and providers are 
> created there. So we'll need {{PlatformCachePluginConfiguration}} and 
> {{PlatformCachePluginProvider}} on Java side.



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

[jira] [Commented] (IGNITE-4457) Define cache plugin API in .NET

2016-12-22 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on IGNITE-4457:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/1375

IGNITE-4457 Define cache plugin API in .NET



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4457

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1375.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1375


commit 8001c3838e2b13edaf8fe159b3a98691b6110089
Author: Pavel Tupitsyn 
Date:   2016-12-22T11:09:01Z

IGNITE-4457 Define cache plugin API in .NET




> Define cache plugin API in .NET
> ---
>
> Key: IGNITE-4457
> URL: https://issues.apache.org/jira/browse/IGNITE-4457
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Define cache plugin API in .NET similar to Java API:
> * {{CacheConfiguration.PluginConfigurations}}
> * {{ICachePluginProvider}}
> * {{ICachePluginContext}}
> Fundamental difference to Ignite plugins (IGNITE-4441), which are local, is 
> that {{CachePluginConfiguration}} is sent to remote nodes and providers are 
> created there. So we'll need {{PlatformCachePluginConfiguration}} and 
> {{PlatformCachePluginProvider}} on Java side.



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

[jira] [Commented] (IGNITE-4457) Define cache plugin API in .NET

2016-12-22 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn commented on IGNITE-4457:


Can't add tests for invalid cache providers due to IGNITE-4474

> Define cache plugin API in .NET
> ---
>
> Key: IGNITE-4457
> URL: https://issues.apache.org/jira/browse/IGNITE-4457
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Define cache plugin API in .NET similar to Java API:
> * {{CacheConfiguration.PluginConfigurations}}
> * {{ICachePluginProvider}}
> * {{ICachePluginContext}}
> Fundamental difference to Ignite plugins (IGNITE-4441), which are local, is 
> that {{CachePluginConfiguration}} is sent to remote nodes and providers are 
> created there. So we'll need {{PlatformCachePluginConfiguration}} and 
> {{PlatformCachePluginProvider}} on Java side.



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

[jira] [Commented] (IGNITE-4457) Define cache plugin API in .NET

2016-12-21 Thread Pavel Tupitsyn (JIRA) 

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

Pavel Tupitsyn commented on IGNITE-4457:


{{CachePluginManager.stop0}} uses reverse iterator incorrectly and does not 
actually stop cache plugins. Fixed.

> Define cache plugin API in .NET
> ---
>
> Key: IGNITE-4457
> URL: https://issues.apache.org/jira/browse/IGNITE-4457
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Define cache plugin API in .NET similar to Java API:
> * {{CacheConfiguration.PluginConfigurations}}
> * {{ICachePluginProvider}}
> * {{ICachePluginContext}}
> Fundamental difference to Ignite plugins (IGNITE-4441), which are local, is 
> that {{CachePluginConfiguration}} is sent to remote nodes and providers are 
> created there. So we'll need {{PlatformCachePluginConfiguration}} and 
> {{PlatformCachePluginProvider}} on Java side.



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