Do the docs need to be clarified about Drill lack of support for variable-length CHAR in the Supported Data Types <http://kristinehahn.github.io/drill/docs/supported-data-types/>--these are the SQL types? I think so. We need to ditch the example of CHAR(30) for sure. The docs say that the Hive CHAR type is mapped to the SQL VARCHAR type, but the ramifications of this mapping with regard to using Hive don't jump out at you. We need to spell it out using a Hive example, right?
Kristine Hahn Sr. Technical Writer 415-497-8107 @krishahn skype:krishahn On Fri, Sep 4, 2015 at 7:20 AM, Christopher Matta <[email protected]> wrote: > It doesn’t look like Drill 1.1.0 supports the Hive CHAR type? > > In Hive: > > create table development.foo > ( > bad CHAR(10) > ); > > And then in sqlline: > > > use `hive.development`; > > select * from foo; > Error: PARSE ERROR: Unsupported Hive data type CHAR. > > Following Hive data types are supported in Drill INFORMATION_SCHEMA: > BOOLEAN, BYTE, SHORT, INT, LONG, FLOAT, DOUBLE, DATE, TIMESTAMP, > BINARY, DECIMAL, STRING, VARCHAR, LIST, MAP, STRUCT and UNION > [Error Id: 58bf3940-3c09-4ad2-8f52-d052dffd4b17 on dtpg05:31010] > (state=,code=0) > > This Jira <https://issues.apache.org/jira/browse/DRILL-1570> was closed > back in October, but it would seem that CHAR isn’t currently supported. > Will this be in 1.2.0? > > Chris [email protected] > 215-701-3146 > >
