[
https://issues.apache.org/jira/browse/SYSTEMML-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Boehm closed SYSTEMML-2538.
------------------------------------
Fix Version/s: SystemML 1.3
Resolution: Fixed
Thanks again for catching this. In detail, it was indeed an issue of invalid
renames for csv/mm/textcell, which only occurred in special cases of forced
singlenode computation (as done in the example run script) while in cluster
environments and our testsuite, we run in hybrid by default (where
distributed/in-memory reblocks always create new metadata objects). The issue
has been fixed with
https://github.com/apache/systemml/commit/47924e6aced3dac0768756c7dfec932d696b6a3f.
> Input CSV file is renamed by simple load and save script
> --------------------------------------------------------
>
> Key: SYSTEMML-2538
> URL: https://issues.apache.org/jira/browse/SYSTEMML-2538
> Project: SystemML
> Issue Type: Bug
> Components: APIs, Compiler
> Affects Versions: SystemML 1.3
> Reporter: Samuel Kogler
> Assignee: Matthias Boehm
> Priority: Minor
> Fix For: SystemML 1.3
>
> Attachments: rename_bug.dml
>
>
> A simple script that reads a CSV file and writes it to an output file just
> renames the input file to the output file.
> This optimization should not be applied to input files but only to temporary
> scratch files.
> Judging from quick local checks, this bug does not seem to affect
> data_type='frame' inputs, but only data_type='matrix'. Test script is
> attached.
> Tested on current master git branch
> (ef8b551103085b73d0b471db9df6c5c0748f7d94) on the file
> {noformat}
> src/test/scripts/functions/io/csv/in/transfusion_1.csv
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
