You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2020/04/09 13:05:00 UTC
[jira] [Comment Edited] (FLINK-17067) CatalogManager#createTable
and createTemporaryTable should provide consistent semantics
[ https://issues.apache.org/jira/browse/FLINK-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079315#comment-17079315 ]
Timo Walther edited comment on FLINK-17067 at 4/9/20, 1:04 PM:
---------------------------------------------------------------
A reason for the different semantics might be because `OR REPLACE` is more useful in a programming API. But if we don't need to deprecate public API, +1 for consistency.
was (Author: twalthr):
A reason for the different semantics might be because, `OR REPLACE` is more useful in a programming API. But if we don't need to deprecate public API, +1 for consistency.
> CatalogManager#createTable and createTemporaryTable should provide consistent semantics
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-17067
> URL: https://issues.apache.org/jira/browse/FLINK-17067
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Affects Versions: 1.10.0
> Reporter: Zhenghua Gao
> Priority: Major
> Fix For: 1.11.0
>
>
> Currently CatalogManager#createTable provides [IF NOT EXISTS] semantic and CatalogManager#createTemporaryTable provides [OR REPLACE] semantic. IMO they should provide consistent semantics: [IF NOT EXISTS] or [OR REPLACE].
> I prefer [IF NOT EXISTS] since we didn't support [OR REPLACE] in table DDL(and view DDL) currently.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)