You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@systemml.apache.org by "Mike Dusenberry (JIRA)" <ji...@apache.org> on 2016/03/16 18:56:33 UTC

[jira] [Updated] (SYSTEMML-579) Packing our algorithm scripts into JAR

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

Mike Dusenberry updated SYSTEMML-579:
-------------------------------------
    Description: 
Packing our algorithm to JAR without look into the user's filesystem.

We should look into the possibility of packing our algorithm scripts into the JAR during build time as perhaps a Maven "resource" that would be available to the Java process without needing to look into the user's filesystem.  This should help with the Scala API introduced in SYSTEMML-580.  One issue I see with the current approach is if a user wishes to attach the SystemML JAR to a cloud notebook (such as Databricks Cloud) in which an environment variable may not be able to be set, the API will not function.

  was:Packing our algorithm to JAR without look into the user's filesystem.


> Packing our algorithm scripts into JAR
> --------------------------------------
>
>                 Key: SYSTEMML-579
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-579
>             Project: SystemML
>          Issue Type: Task
>          Components: Algorithms, APIs
>    Affects Versions: SystemML 0.9
>            Reporter: Tommy Yu
>            Priority: Minor
>
> Packing our algorithm to JAR without look into the user's filesystem.
> We should look into the possibility of packing our algorithm scripts into the JAR during build time as perhaps a Maven "resource" that would be available to the Java process without needing to look into the user's filesystem.  This should help with the Scala API introduced in SYSTEMML-580.  One issue I see with the current approach is if a user wishes to attach the SystemML JAR to a cloud notebook (such as Databricks Cloud) in which an environment variable may not be able to be set, the API will not function.



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