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/23 04:01:00 UTC

[jira] [Closed] (FLINK-12582) Alteration APIs in catalogs should check existing object and new object are of the same class

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

Bowen Li closed FLINK-12582.
----------------------------
    Resolution: Fixed

merged in 1.9.0: aca9c018a4b26e50333c33426e77323cbb9b7960

> Alteration APIs in catalogs should check existing object and new object are of the same class
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLINK-12582
>                 URL: https://issues.apache.org/jira/browse/FLINK-12582
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Bowen Li
>            Assignee: Bowen Li
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Alterations in catalogs should check existing object and new object are of the same class. 
> Most of them currently don't, e.g. you can alter an existing generic table with a new hive table in GenericInMemoryCatalog.



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