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

Posted to issues@flink.apache.org by "Bowen Li (JIRA)" <ji...@apache.org> on 2019/05/15 21:17:01 UTC

[jira] [Updated] (FLINK-12452) alterTable() should ensure existing base table and the new one are of the same type

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

Bowen Li updated FLINK-12452:
-----------------------------
    Description: Currently all catalogs doesn't check if existing base table and the new one are of the same type in alterTable(). We should add the check to all catalogs  (was: Currently all catalogs does check if existing base table and the new one are of the same type in alterTable(). We should add the check to all catalogs)

> alterTable() should ensure existing base table and the new one are of the same type
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-12452
>                 URL: https://issues.apache.org/jira/browse/FLINK-12452
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Connectors / Hive, Table SQL / API
>            Reporter: Bowen Li
>            Assignee: Bowen Li
>            Priority: Major
>             Fix For: 1.9.0
>
>
> Currently all catalogs doesn't check if existing base table and the new one are of the same type in alterTable(). We should add the check to all catalogs



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