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

Jiarong Wei commented on CALCITE-1424:
--------------------------------------

Yes, using {{DruidType}} is more reasonable and {{DOUBLE}} is less confusing!

> Druid type is called FLOAT, not DOUBLE
> --------------------------------------
>
>                 Key: CALCITE-1424
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1424
>             Project: Calcite
>          Issue Type: Bug
>          Components: druid
>            Reporter: Jiarong Wei
>            Assignee: Julian Hyde
>             Fix For: 1.11.0
>
>
> Currently the supported column types in Druid adapter are: {{LONG}}, 
> {{DOUBLE}}, {{STRING}} and {{hyperUnique}}
> There's no clue to show Druid has {{DOUBLE}} as its column type. But instead 
> it should be {{FLOAT}} as mentioned in [Druid 
> Documentation|http://druid.io/docs/latest/querying/segmentmetadataquery.html]:
> bq. Dimension columns will have type STRING. Metric columns will have type 
> FLOAT or LONG or name of the underlying complex type such as hyperUnique in 
> case of COMPLEX metric. Timestamp column will have type LONG.
> Fangjin Yang didn't mentioned it in related posts either. See 
> [1|https://groups.google.com/forum/#!msg/druid-development/U_24K3FLveM/kE-T1NluqHsJ]
>  and 
> [2|https://groups.google.com/forum/#!msg/druid-development/cVTJrrxq7kI/MhM3FF3g0x8J]



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

Reply via email to