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 2020/04/20 17:49:00 UTC

[jira] [Commented] (IGNITE-12676) .NET: Add partition-based AffinityCall and AffinityRun overloads

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

Pavel Tupitsyn commented on IGNITE-12676:
-----------------------------------------

[~ashapkin] PR ready, please review: https://github.com/apache/ignite/pull/7701

> .NET: Add partition-based AffinityCall and AffinityRun overloads
> ----------------------------------------------------------------
>
>                 Key: IGNITE-12676
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12676
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add partition-based AffinityCall and AffinityRun overloads to ICompute.See corresponding methods in Java (IgniteCompute).
> Additionally, current affinity methods work through PlatformAbstractTask, which does not lock partitions. We should refactor existing AffinityCall and AffinityRun overloads to call corresponding IgniteCompute APIs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)