You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@systemml.apache.org by "Matthias Boehm (JIRA)" <ji...@apache.org> on 2016/02/17 09:14:18 UTC
[jira] [Resolved] (SYSTEMML-491) Runtime Platform Should
Automatically Be Set To Singlenode When Executed Locally With Scala/Java
[ https://issues.apache.org/jira/browse/SYSTEMML-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Boehm resolved SYSTEMML-491.
-------------------------------------
Resolution: Won't Fix
I'm marking this as won't fix because "standalone" is orthogonal to execution modes - the only difference to our normal distribution is a different packing with all required libraries. Adding custom logic inside SystemML would break the design of having *exactly* the same code path.
> Runtime Platform Should Automatically Be Set To Singlenode When Executed Locally With Scala/Java
> ------------------------------------------------------------------------------------------------
>
> Key: SYSTEMML-491
> URL: https://issues.apache.org/jira/browse/SYSTEMML-491
> Project: SystemML
> Issue Type: Bug
> Reporter: Mike Dusenberry
>
> Currently, the default runtime platform is set to "hybrid" mode, which is an automatically optimized hybrid between single-node and Hadoop MR. When running locally with Scala/Java (such as in our "standalone" distribution package), we should automatically detect and change the mode to the correct setting of "singlenode". Of course, our {{runStandaloneSystemML.sh}} and {{bin/systemml}} scripts append this runtime mode explicitly, but a user shouldn't have to do this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)