[
https://issues.apache.org/jira/browse/DRILL-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493536#comment-14493536
]
Adam Gilmore commented on DRILL-2373:
-------------------------------------
Hey [~jaltekruse] - I'll look into what we can do for that testing. I imagine
we don't have any of the REST API tested at the moment? I imagine that will
mean spinning up the server itself to execute the queries, so it might be good
to get some thoughts on the best way to set that up as a test harness. What
are your thoughts?
Fair call on making the web UI work smoothly. I think this would just be good
so that people can consume the REST API nicely elsewhere.
> 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)
