systemml-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Boehm (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SYSTEMML-1840) Transform spec literals should be checked during validate
Date Tue, 15 Aug 2017 20:04:01 GMT

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

Matthias Boehm closed SYSTEMML-1840.
------------------------------------

> Transform spec literals should be checked during validate
> ---------------------------------------------------------
>
>                 Key: SYSTEMML-1840
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-1840
>             Project: SystemML
>          Issue Type: Bug
>            Reporter: Matthias Boehm
>            Assignee: Matthias Boehm
>             Fix For: SystemML 1.0
>
>
> Currently, there is no validation happening for transform specifications during initial
compilation. This is very annoying, especially when trying to encode large files, which takes
a while to read in, just to find out that the given transform specification was invalid json.
Here is an example:
> {code}
> Caused by: org.apache.wink.json4j.JSONException: Expecting '{' on line 1, column 4 instead,
obtained token: 'Token: String - 'ids''
>         at org.apache.wink.json4j.internal.Parser.parseObject(Parser.java:193)
>         at org.apache.wink.json4j.internal.Parser.parse(Parser.java:130)
>         at org.apache.wink.json4j.internal.Parser.parse(Parser.java:95)
>         at org.apache.wink.json4j.JSONObject.<init>(JSONObject.java:138)
>         at org.apache.sysml.runtime.transform.encode.EncoderFactory.createEncoder(EncoderFactory.java:56)
> {code}
> This task aims to parse the transform specification if its available as a literal string
during the language validation step.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message