You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Ramana Inukonda Nagaraj (JIRA)" <ji...@apache.org> on 2014/04/15 20:19:14 UTC

[jira] [Created] (DRILL-521) INFORMATION_SCHEMA breaks if you have hive table with unsupported datatypes

Ramana Inukonda Nagaraj created DRILL-521:
---------------------------------------------

             Summary: INFORMATION_SCHEMA breaks if you have hive table with unsupported datatypes
                 Key: DRILL-521
                 URL: https://issues.apache.org/jira/browse/DRILL-521
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Ramana Inukonda Nagaraj


repro:
Create some hive tables having datatypes which are valid in drill. Ie no struct, arrays etc. 

Select * from INFORMATION_SCHEMA.TABLES works at this point.

Create a hive table containing complex data types: Example:

CREATE TABLE test_serializer(string1 STRING,
                             int1 INT,
                             tinyint1 TINYINT,
                             smallint1 SMALLINT,
                             bigint1 BIGINT,
                             boolean1 BOOLEAN,
                             float1 FLOAT,
                             double1 DOUBLE,
                             list1 ARRAY<STRING>,
                             map1 MAP<STRING,INT>,
                             struct1 STRUCT<sint:INT,sboolean:BOOLEAN,sstring:STRING>,
                             enum1 STRING,
                             nullableint INT,
                             bytes1 BINARY,
                             fixed1 BINARY)
 ROW FORMAT DELIMITED FIELDS TERMINATED BY ',' COLLECTION ITEMS TERMINATED BY ':' MAP KEYS TERMINATED BY '#' LINES TERMINATED BY '\n'
 STORED AS TEXTFILE;

After this INFORMATION_SCHEMA queries fail  with 
message: "Failure while parsing sql. < ValidationException:[ java.lang.RuntimeException: Unknown or unsupported hive type ] < RuntimeException:[ Unknown or unsupported hive type ]"




--
This message was sent by Atlassian JIRA
(v6.2#6252)