|author||Boris Shulman <firstname.lastname@example.org>||Thu Feb 18 22:13:00 2016 -0800|
|committer||Andrew Chung <email@example.com>||Mon Feb 22 17:06:21 2016 -0800|
[REEF-1196] Allow specifying runtime name in evaluator request This changeset addresses the issue by: 1)Adding runtime name to the evaluator request 2)Propagating runtime name to the evaluatiormanager 3)Adding runtime name to the Resource Events implementations JIRA: [REEF-1196](https://issues.apache.org/jira/browse/REEF-1196) Pull Request: Closes #848
Apache REEF™ (Retainable Evaluator Execution Framework) is a scale-out computing fabric that simplifies the development of Big Data applications on top of resource managers (e.g., Apache YARN and Mesos). For example, Azure Stream Analytics is built on REEF and Hadoop.
This file will cover the very basics of compiling and testing REEF. Much more detailed information can be found in the following places:
The developer mailinglist is the best way to reach REEF‘s developers when the above aren’t sufficient.
mvnis in your
protocis on your
The Java side of REEF is built using Apache Maven. To build, execute:
mvn -DskipTests clean install
To test, execute:
Note that the tests will take several minutes to complete. You will also see stack traces fly by. Not to worry: those are part of the tests that test REEF's error reporting.
REEF.NET uses REEF Java. In fact, the instructions below build REEF Java as part of building REEF.NET. Hence, the same requirements apply.
To build and test in Visual Studio, open
Alternatively, you can build REEF.NET from a developer command line via:
To test, execute the following command thereafter:
vstest.console.exe .\lang\cs\bin\x64\Debug\Org.Apache.REEF.Tests\Org.Apache.REEF.Tests.dll /Platform:x64