You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/08/30 18:48:00 UTC

[jira] [Updated] (IMPALA-4379) Fix Kudu table type checking

     [ https://issues.apache.org/jira/browse/IMPALA-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Rodoni updated IMPALA-4379:
--------------------------------
    Docs Text:   (was: Doc type differences)

> Fix Kudu table type checking
> ----------------------------
>
>                 Key: IMPALA-4379
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4379
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Kudu_Impala
>            Reporter: Matthew Jacobs
>            Assignee: Matthew Jacobs
>            Priority: Critical
>              Labels: kudu
>             Fix For: Impala 2.8.0
>
>
> Creating Kudu tables shouldn't allow types not supported by Kudu (e.g. VAR/CHAR, DECIMAL, TIMESTAMP, collection types). The behavior is inconsistent, for some types it throws in the catalog, for VAR/CHAR these become strings. These should all fail w/ analysis exceptions until Kudu supports these types.
> Similarly, external tables cannot contain Kudu types that Impala doesn't support (e.g. UNIXTIME_MICROS, BINARY). This does fail, but we need tests to verify.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org