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

Adam Gilmore commented on DRILL-2373:
-------------------------------------

No problem - I see it.  I'll fix and post the patch again to the review board.

> 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: Sudheesh Katkam
>            Priority: Minor
>             Fix For: 1.1.0
>
>         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)

Reply via email to