Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5890

DROP TABLE IF EXISTS should not generate errors for non existing tables

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 23.10.4
    • None
    • None
    • 2025-2

    Description

      running drop table if exists on a non existing table generates errors in the columnstore logs.
      E 23 CAL0001: Table does not exist in ColumnStore.

      This is misleading as it indicates an error where in reality there is none.

      Also it would be great if the message actualy told you what table it is talking about.

      Steps to reproduce:

      create database test;
      drop table if exists test.does_not_exist;

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MCOL-4270 DROP COLUMN IF EXISTS fails if the column is already present

          • Major - Major loss of function.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            mgolisch Michael Golisch created issue -
            mgolisch Michael Golisch made changes -
            Field Original Value New Value
            Description running drop table if exists on a non existing table generates errors in the columnstore logs.
            E 23 CAL0001: Table does not exist in ColumnStore.

            This is misleading as it indicates an error where in reality there is none.

            Also it would be great if the message actualy told you what table it is talking about.

            Steps to reproduce:

            create database test;
            drop table if exist test.does_not_exist;             		running drop table if exists on a non existing table generates errors in the columnstore logs.
            E 23 CAL0001: Table does not exist in ColumnStore.

            This is misleading as it indicates an error where in reality there is none.

            Also it would be great if the message actualy told you what table it is talking about.

            Steps to reproduce:

            create database test;
            drop table if exists test.does_not_exist;
            leonid.fedorov Leonid Fedorov made changes -
            leonid.fedorov Leonid Fedorov made changes -
            Assignee Leonid Fedorov [ JIRAUSER48443 ]
            allen.herrera Allen Herrera made changes -
            Fix Version/s 23.10.4 [ 29991 ]
            Sprint 2025-2 [ 788 ]
            leonid.fedorov Leonid Fedorov made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            leonid.fedorov Leonid Fedorov made changes -
            Status In Progress [ 3 ] In Testing [ 10301 ]
            abukhalov Aleksei Bukhalov made changes -
            Resolution Fixed [ 1 ]
            Status In Testing [ 10301 ] Closed [ 6 ]

            People

              leonid.fedorov Leonid Fedorov
              mgolisch Michael Golisch
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.