[jira] [Updated] (CALCITE-4533) Incorrect semantics of REPLACE and IF NOT EXISTS keywords in CREATE TABLE/SCHEMA commands

["Vladimir Ozerov (Jira)" <ji...@apache.org>]

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

Vladimir Ozerov updated CALCITE-4533:
-------------------------------------
    Summary: Incorrect semantics of REPLACE and IF NOT EXISTS keywords in CREATE TABLE/SCHEMA commands  (was: Fix handling of REPLACE and IF NOT EXISTS keywords for CREATE TABLE/SCHEMA commands)

> Incorrect semantics of REPLACE and IF NOT EXISTS keywords in CREATE TABLE/SCHEMA commands
> -----------------------------------------------------------------------------------------
>
>                 Key: CALCITE-4533
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4533
>             Project: Calcite
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 1.26.0
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> Presently, the {{ServerDdlExecutor}} incorrectly process some keywords:
> # {{CREATE SCHEMA IF NOT EXISTS}} overwrites the existing schema
> # {{CREATE OR REPLACE TABLE}} doesn't replace the table if the table exists
> The goal of this ticket is to unify the handling of {{IF NOT EXISTS}} and {{REPLACE}} keywords for these two commands.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)