You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Andrew Chung (JIRA)" <ji...@apache.org> on 2016/02/03 19:12:39 UTC
[jira] [Updated] (REEF-1180) Split REEFClient submission parameter
file into per-application and per-job
[ https://issues.apache.org/jira/browse/REEF-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Chung updated REEF-1180:
-------------------------------
Issue Type: New Feature (was: Improvement)
> Split REEFClient submission parameter file into per-application and per-job
> ---------------------------------------------------------------------------
>
> Key: REEF-1180
> URL: https://issues.apache.org/jira/browse/REEF-1180
> Project: REEF
> Issue Type: New Feature
> Components: REEF.NET, REEF.NET Client
> Reporter: Andrew Chung
> Assignee: Andrew Chung
>
> Loosely defining the terms used here:
> Application: A REEF application.
> Job: Submissions of REEF applications to the RM framework.
> In other words, there can be many REEF jobs, but there is only one REEF application, from the RM framework point of view.
> Currently, we package both application and job parameters into the same Avro parameter file. We should break the file down into two parameter files -- one for application and another for job, such that we can generate a package once and re-use it many times as long as the user supplies the job parameters and the package (or the location of the package).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)