[jira] [Comment Edited] (DRILL-2373) JSON query request returns all types as strings

["Jason Altekruse (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494235#comment-14494235 ] 

Jason Altekruse edited comment on DRILL-2373 at 4/14/15 3:21 PM:
-----------------------------------------------------------------

Completely agree, drill itself is solving a lot of the issues that consumers of JSON APIs often experience, it makes no sense to re-introduce poor typing for consumers of our output. You might be interested in taking a look at a feature currently in review to add extended JSON support, to allow us to read in an export a greater variety of data types, similar to the approach taken by MongoDB. DRILL-2695


was (Author: jaltekruse):
Completely agree, we are solving a lot of the same issues that consumers of JSON APIs in drill itself, it makes no sense to re-introduce poor typing for consumers of our output. You might be interested in taking a look at a feature currently in review to add extended JSON support, to allow us to read in an export a greater variety of data types, similar to the approach taken by MongoDB. DRILL-2695

> JSON query request returns all types as strings
> -----------------------------------------------
>
>                 Key: DRILL-2373
>                 URL: https://issues.apache.org/jira/browse/DRILL-2373
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - HTTP
>    Affects Versions: 0.7.0, 0.8.0
>            Reporter: Adam Gilmore
>            Assignee: Adam Gilmore
>            Priority: Minor
>         Attachments: DRILL-2373.1.patch.txt, DRILL-2373.2.patch.txt
>
>
> I'm not sure if the query JSON endpoint is a valid, documented feature of Drill, but at the moment it returns all results as strings.
> So, for example:
> {code}select count(*) from cp.`employee.json`{code}
> Will return "1155" (as a string) as opposed to 1155 (as a numeric JSON value).
> It really should be returning numeric values as proper JSON numeric values.  Same should apply for boolean values.
> How we handle other data types (i.e. dates, intervals, timestamps, etc.) needs discussion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)