| commit | 93ef5013d6b02c5294591619d22a51efdcd07221 | [log] [tgz] |
|---|---|---|
| author | roganc <rocarr@microsoft.com> | Wed Aug 02 12:54:09 2017 -0700 |
| committer | Doug Service <dougservice@apache.org> | Tue Aug 08 01:14:48 2017 +0000 |
| tree | 54d376efcd2e96afd41ad61d07b104d392cfc0bc | |
| parent | 19ed1a120854015f90370a819006510c8a3419dd [diff] |
[REEF-1849] Fix CoreCLR incompatibilities in REEF Network
This addressed the issue by
* Switching `System.Runtime.Caching.MemoryCache` to
`Microsoft.Extensions.Caching.Memory.MemoryCache` in `NameCache`
* Creating a new API to use the new caching mechanism
* Marking the old API as Obsolete
* Changing the old API to use the old parameters to make the new
cache, giving warnings about parameters
* Adding the necessary parameter to the `NameCacheConfiguration`
* Marking the old parameters as obsolete
* Removing unused internal methods from `NameCache`
JIRA:
[REEF-1849](https://issues.apache.org/jira/browse/REEF-1849)
Pull request:
This closes #1349
Apache REEF™ (Retainable Evaluator Execution Framework) is a library for developing portable applications for cluster resource managers such as Apache Hadoop YARN or Apache Mesos. For example, Microsoft Azure Stream Analytics is built on REEF and Hadoop.
Detailed information on REEF can be found in the following places:
The developer mailing list is the best way to reach REEF‘s developers when the above aren’t sufficient.
| Component | OS | Status |
|---|---|---|
| REEF Java | Ubuntu |  |
| REEF.NET | Windows |
| Java | .NET | |
|---|---|---|
| Build & run unit tests | java\BUILD.md | cs\BUILD.md |
