[jira] [Commented] (REEF-71) Expose the static part of a runtime's Driver configuration

["Markus Weimer (JIRA)" <ji...@apache.org>]

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

Markus Weimer commented on REEF-71:
-----------------------------------

I did some digging into this. It seems harder than first thought: Much of the runtime-specific driver configuration is indeed *not* static. Instead, it is derived off of the client-side configuration and sometimes even computed at runtime. We might have to mirror that code into C# in order to get a java-free client.

> Expose the static part of a runtime's Driver configuration
> ----------------------------------------------------------
>
>                 Key: REEF-71
>                 URL: https://issues.apache.org/jira/browse/REEF-71
>             Project: REEF
>          Issue Type: Sub-task
>            Reporter: Markus Weimer
>
> The REEF Runtime API requires runtimes to bind certain implementations for the Driver to work (e.g. for resource allocation, return, ...). Additionally, a runtime might bind additional implementations and parameters. Today, these bindings occur during job submission, typically in a runtime's implementation of {{JobSubmissionHandler}}.
> There is no API by which REEF could request just those additional bindings from a runtime. This hinders the creation of "template" Configuration files to be used by the CLR side. This JIRA tracks the progress towards creating such an API.



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