[jira] [Commented] (SYSTEMML-995) MLContext dataframe-frame conversion with index column & vector column

["Mike Dusenberry (JIRA)" <ji...@apache.org>]

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

Mike Dusenberry commented on SYSTEMML-995:
------------------------------------------

Also, disabling the reblock rewrite above lead to issues on passing in SystemML matrix objects from one script to another with MLContext due to the matrix metadata output info being set to {{OutputInfo.BinaryCellOutputInfo}} instead of {{OutputInfo.BinaryBlockOutputInfo}}.

> MLContext dataframe-frame conversion with index column & vector column
> ----------------------------------------------------------------------
>
>                 Key: SYSTEMML-995
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-995
>             Project: SystemML
>          Issue Type: Bug
>          Components: APIs
>    Affects Versions: SystemML 0.11
>            Reporter: Matthias Boehm
>            Priority: Blocker
>
> MLContext currently always assumes data frame to frame conversion without existing index column. Since the user cannot communicate the existence of this column, the data conversion leads to incorrect results as an additional column is included in the output frame. We need make the MLContext handling of frames consistent with the handling of matrices.
> Additionally, the conversion code in {{MLContextConversionUtil.dataFrameToFrameObject()}} does not yet take into account frames with vectors, although the recent addition adds this support in the underlying {{FrameRDDConverterUtils.java}} class.  Therefore, the number of columns set when {{mc == null}} is incorrect.
> Thanks [~mwdusenb@us.ibm.com] for catching this issue. cc [~acs_s] [~deron]



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