You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Sapego (JIRA)" <ji...@apache.org> on 2016/08/05 17:46:20 UTC

[jira] [Commented] (IGNITE-1680) CPP: Implement basic API for user entry point lookup

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

Igor Sapego commented on IGNITE-1680:
-------------------------------------

Current plan is to introduce module manager that can dynamically look up functions in loaded modules and to ask user to register all invoke-jobs using another manager class. After that we only need to pass the identifier of the job to remote node together with the serialized job instance and the argument. On the receiving node we are going to read job identifier, perform job lookup using module manager and call the job or throw an exception if there are no such job on the remote node.

Note that we don't know how to deserialize the invoke-job until we found it, so actually we should not only register job when user registers it but also register job deserializer.

> CPP: Implement basic API for user entry point lookup
> ----------------------------------------------------
>
>                 Key: IGNITE-1680
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1680
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Igor Sapego
>            Assignee: Igor Sapego
>              Labels: cpp, roadmap
>             Fix For: 1.8
>
>
> Need to implement IgniteCompute class for C++ with one basic method IgniteCompute::Call(...) which will provide basic remote job execution API.



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