[SYSTEMDS-1840] Transform spec literals should be checked during validate

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: SystemML 0.15
• Assignee: Matthias Boehm
• Reporter: Matthias Boehm
• Created: 15/Aug/17 05:40
• Updated: 09/Sep/17 03:49
• Resolved: 15/Aug/17 20:03

Description

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:

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)

This task aims to parse the transform specification if its available as a literal string during the language validation step.