reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (REEF-92) Restructure tests and examples
Date Sat, 09 Apr 2016 00:01:32 GMT

     [ https://issues.apache.org/jira/browse/REEF-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Markus Weimer updated REEF-92:
------------------------------
    Component/s: REEF Examples

> Restructure tests and examples
> ------------------------------
>
>                 Key: REEF-92
>                 URL: https://issues.apache.org/jira/browse/REEF-92
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF Examples
>            Reporter: Markus Weimer
>            Assignee: Gyeongin Yu
>            Priority: Minor
>
> We have a great many examples and tests in REEF, all of which we'd like
> to maintain in runnable form for all runtimes (local, YARN, HDInsight,
> Mesos, ...). Also, we shouldn't impose undue dependencies, e.g.
> depending on YARN libraries when all we want is to run locally, for
> instance.
> Right now, this melange of goals and challenges is poorly reflected in
> the project structure. For instance, reef-examples and reef-tests both
> depend on reef-runtime-yarn *and* reef-runtime-local. Yet, we have
> reef-examples-hdinsight to capture that dependency separately.
> Based on the discussion on the mailing list, I propose the following change: Create sub-projects
in reef-examples and reef-tests: one
> with the core code, and one per runtime that captures the dependency on
> that runtime as well as the launch code on that runtime. This makes it obvious what we
expect from new integration
> tests and examples. 



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

Mime
View raw message