Great, thanks!

--
Jacques Nadeau
CTO and Co-Founder, Dremio

On Tue, Sep 8, 2015 at 5:27 AM, Nathaniel Auvil <[email protected]>
wrote:

> I aped Chris's fragments to reproduce in:
> https://issues.apache.org/jira/browse/DRILL-3745
>
> On Tue, Sep 8, 2015 at 1:36 AM, Jacques Nadeau <[email protected]> wrote:
>
> > It looks like we need a JIRA to make sure this gets fixed. Nathaniel,
> will
> > you post one?
> >
> > --
> > Jacques Nadeau
> > CTO and Co-Founder, Dremio
> >
> > On Fri, Sep 4, 2015 at 10:35 AM, Nathaniel Auvil <
> > [email protected]>
> > wrote:
> >
> > > without CHAR support, drill can not be used in Squirrel when the hive
> > > plugin is enabled and a hive table has CHAR
> > >
> > > On Fri, Sep 4, 2015 at 12:00 PM, Venki Korukanti <
> > > [email protected]>
> > > wrote:
> > >
> > > > I think we can support this. CHAR was added in recent versions of
> Hive.
> > > It
> > > > got missed when we upgraded the supported Hive versions in plugin.
> > > >
> > > > Thanks
> > > > Venki
> > > >
> > > > On Fri, Sep 4, 2015 at 8:58 AM, Christopher Matta <[email protected]>
> > > wrote:
> > > >
> > > > > According to this page:
> > > > >
> > > >
> > >
> >
> http://kristinehahn.github.io/drill/docs/hive-to-drill-data-type-mapping/
> > > > > it
> > > > > looks like Drill should convert CHAR to VARCHAR, but it's not.
> > > > >
> > > > > On Friday, September 4, 2015, Christopher Matta <[email protected]>
> > > wrote:
> > > > >
> > > > > > Does this mean there aren't plans to support this data type? What
> > > about
> > > > > > Hive comparability?
> > > > > >
> > > > > > On Friday, September 4, 2015, Kristine Hahn <[email protected]
> > > > > > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
> > > > > >
> > > > > >> 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
> > > > > >> > ​
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Chris Matta
> > > > > > [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]
> ');>
> > > > > > 215-701-3146
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Chris Matta
> > > > > [email protected]
> > > > > 215-701-3146
> > > > >
> > > >
> > >
> >
>

Reply via email to