You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2016/10/17 22:56:58 UTC
[jira] [Resolved] (REEF-1642) Check for singletons per
REEFEnvironment, not per entire JVM process
[ https://issues.apache.org/jira/browse/REEF-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Weimer resolved REEF-1642.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.16
Resolved via [#1157|https://github.com/apache/reef/pull/1157]
> Check for singletons per REEFEnvironment, not per entire JVM process
> --------------------------------------------------------------------
>
> Key: REEF-1642
> URL: https://issues.apache.org/jira/browse/REEF-1642
> Project: REEF
> Issue Type: Sub-task
> Components: REEF
> Reporter: Sergiy Matusevych
> Assignee: Sergiy Matusevych
> Labels: assertion, singleton
> Fix For: 0.16
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently some classes, like {{Evaluators}}, assert that there is only one instance of such class per application. This is no longer true with the {{REEFEnvironment}} setting, where a class is a singleton per environment, not per entire JVM process. We need to extend our assertion functionality for such case, and use it in classes like {{Evaluators}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)