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

Assertion failure when using HAVING with constant values

    XMLWordPrintable

Details

    Description

      Caused by this asserion failure
      DBUG_ASSERT(using_unique_constraint ||
      group_buff <= param->group_buff + param->group_length)
      sql_select.cc:create_tmp_table

      Presumably plugin or modified server code sets vtable_mode thd->infinidb_vtable.vtable_state to THD::INFINIDB_DISABLE_VfTABLE in the middle of table creation, that later causes the failure.

      Steps to reproduce. FYI any table is fit.

      MariaDB [cs]> show create table cs1;
      -----------------------------------------------------------------------------------------------------------------------------+

      Table Create Table

      -----------------------------------------------------------------------------------------------------------------------------+

      cs1 CREATE TABLE `cs1` (
      `a` char(1) DEFAULT NULL,
      `d` double DEFAULT NULL
      ) ENGINE=Columnstore DEFAULT CHARSET=latin1

      -----------------------------------------------------------------------------------------------------------------------------+
      1 row in set (0.00 sec)

      MariaDB [cs]> select * from cs1;
      ------------+

      a d

      ------------+

      A 1.2555
      B 2.2555
      A 3.2555
      B 4.2555

      ------------+
      4 rows in set (0.09 sec)

      MariaDB [cs]> select a from cs1 group by a having 'c' = 1;

      Attachments

        Issue Links

          Activity

            People

              David.Hall David Hall (Inactive)
              drrtuy Roman
              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.