[ https://issues.apache.org/jira/browse/ASTERIXDB-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718472#comment-16718472 ]
Michael J. Carey edited comment on ASTERIXDB-2496 at 12/12/18 5:08 AM: ----------------------------------------------------------------------- (The JSON object was probably the most ill-designed example of JSON that I have ever seen - but - very interesting, and thought-provoking. :)) was (Author: dtabass): (The JSON object was probably the most ill-designed example of JSON that I have ever seen - but - very interested, and thought-provoking. :)) > Error response to an overly large object is very misleading > ----------------------------------------------------------- > > Key: ASTERIXDB-2496 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2496 > Project: Apache AsterixDB > Issue Type: Bug > Components: *DB - AsterixDB, FAIL - Failure handling/reporting, HYR > - Hyracks > Affects Versions: 0.9.4 > Reporter: Michael J. Carey > Assignee: Till > Priority: Major > Fix For: 0.9.5 > > > If you try to LOAD a JSON object that exceeds the system's limit, it > complains as follows: > ASX3021: Malformed input stream [HyracksDataException] > This is not very helpful to users - I spent awhile today with one such user. > He had been given a "data set" in the form of a JSON dump file from Firebase, > and it contained exactly one HUGE JSON document. That object was about 90MB, > but it was not malformed - it was perfectly good JSON that was parsable by > Javascript's JSON parser, so the user was puzzled. > In this case the system should have reported that the size was the problem, > e.g., "Incoming object exceeded system size limit". -- This message was sent by Atlassian JIRA (v7.6.3#76005)