You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Sudheesh Katkam (JIRA)" <ji...@apache.org> on 2015/03/04 20:27:38 UTC
[jira] [Assigned] (DRILL-2213) JSON parsing error message doesn't
give file name or context of error
[ https://issues.apache.org/jira/browse/DRILL-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudheesh Katkam reassigned DRILL-2213:
--------------------------------------
Assignee: Sudheesh Katkam
> JSON parsing error message doesn't give file name or context of error
> ---------------------------------------------------------------------
>
> Key: DRILL-2213
> URL: https://issues.apache.org/jira/browse/DRILL-2213
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - JSON
> Reporter: Daniel Barclay (Drill)
> Assignee: Sudheesh Katkam
> Fix For: 0.9.0
>
>
> The error message resulting from trying to read this ill-formed JSON (from a local file):
> {
> "key":"abc"
> "a1":1,
> }
> doesn't say anything about where the error was:
> org.apache.drill.exec.rpc.RpcException: RemoteRpcException: Failure while running fragment., Unexpected character ('"' (code 34)): was expecting comma to separate OBJECT entries
> At absolute minimum, it should include the name of the file or a quote of the text surrounding the error.
> It should include:
> - the name of the file
> - the line and column within the file, and/or a byte (or character) offset
> - some of the text surrounding the error
> - (the "Unexpected ... expecting ..." part it already includes.
> (Note: The "code" in "code 34" is ambiguous. "Code point" or "character number" would be better.
> Actually, the report of the character should include the standard (or just conventional?) Unicode hex notation ("U+0022"). (Including the decimal value too is fine, but that should probably be labeled as decimal, perhaps as ... "U+0022 (34 decimal)".)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)