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

Victoria Markman commented on DRILL-1975:
-----------------------------------------

I think I finally figured out why this document section is so confusing ... 

This section describes SQL language and it should only list types that are 
supported in Drill SQL: 
      * BYTEA, TINYINT, SMALLINT, TEXT are not supported SQL types.
      * CHAR seems to be an alias to a VARCHAR 

There should be another section, that talks about rules of conversion between 
Drill SQL types and types that come from other storage formats, like parquet:
     * What type it is going to be converted to when we CTAS without explicit 
cast 
     *  What type it is going to be converted to when we CTAS with explicit cast
     *  Define behavior on what will happen if we cast to incompatible data type

This bug should be probably assigned to dev/qa, so we can write an initial 
draft.

> Documentation on supported Data Types must be corrected
> -------------------------------------------------------
>
>                 Key: DRILL-1975
>                 URL: https://issues.apache.org/jira/browse/DRILL-1975
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Abhishek Girish
>            Assignee: Bridget Bevens
>
> Documentation on Drill Data Types - 
> https://cwiki.apache.org/confluence/display/DRILL/Data+Types needs to be 
> updated. 
> Text data type must be removed from the below list:
> *Binary Types*
> BYTEA
> VARBINARY
> *Character Types*
> CHAR
> VARCHAR 
> TEXT
> *Date/Time Data Types*
> DATE
> INTERVAL
> Interval Year (stores year and month)
> Interval Day (stores day, hour, minute, seconds, and milliseconds)
> TIME
> TIMESTAMP
> *Integer*
> BIGINT
> INT
> SMALLINT
> TINYINT
> *Numeric Types*
> DECIMAL
> FLOAT 
> DOUBLE PRECISION (FLOAT 8)
> REAL (FLOAT 4) 
> *Boolean Types*
> FALSE
> NULL
> TRUE



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

Reply via email to