You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@systemml.apache.org by "Deron Eriksson (JIRA)" <ji...@apache.org> on 2016/08/31 20:05:20 UTC

[jira] [Commented] (SYSTEMML-889) Remove MLContext Java input output methods

    [ https://issues.apache.org/jira/browse/SYSTEMML-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453220#comment-15453220 ] 

Deron Eriksson commented on SYSTEMML-889:
-----------------------------------------

[~reinwald@us.ibm.com], this is a very good suggestion (to remove the redundancy in the API). [~mwdusenb@us.ibm.com] will investigate.

> Remove MLContext Java input output methods
> ------------------------------------------
>
>                 Key: SYSTEMML-889
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-889
>             Project: SystemML
>          Issue Type: Improvement
>          Components: APIs
>            Reporter: Deron Eriksson
>            Assignee: Mike Dusenberry
>
> The input() and output() methods were added to the MLContext Java/Scala API (on Script class) to support the Python API, since "in" is a reserved word in Python.
> Investigate if it's possible to have the Python API call the Java in() method. If it is, have the Python input() method call the Java in() method, and have the Python output() method call the Java out() method. Then, remove the input() and output() methods from the Java Script class since these methods are redundant.



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