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

in a transaction, insert..select fails +multinode+columnstore_use_import_for_batchinsert=ON

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 22.08.3, 22.08.4, 22.08.7
    • 22.08.8
    • None

    Description

      Build tested: 22.08.03, 22.8.4, 22.08.7

      On a multi-node cluster, in a transaction, insert..select reported rows inserted, but query show empty table.
      with columnstore_use_import_for_batchinsert=ON

      MariaDB [mytest]> create table t1 (c1 int) engine=columnstore;
      Query OK, 0 rows affected (0.119 sec)
       
      MariaDB [mytest]> insert into t1 values (1),(2);
      Query OK, 2 rows affected (0.132 sec)
      Records: 2  Duplicates: 0  Warnings: 0
       
      MariaDB [mytest]> select * from t1;
      +------+
      | c1   |
      +------+
      |    1 |
      |    2 |
      +------+
      2 rows in set (0.023 sec)
       
      MariaDB [mytest]> create table t2 (c1 int) engine=columnstore;
      Query OK, 0 rows affected (0.209 sec)
       
      MariaDB [mytest]> start transaction;
      Query OK, 0 rows affected (0.000 sec)
       
      MariaDB [mytest]> insert into t2 select * from t1;
      Query OK, 2 rows affected (1.125 sec)
      Records: 2  Duplicates: 0  Warnings: 0
       
      MariaDB [mytest]> select * from t2;
      Empty set (0.022 sec)
       
      MariaDB [mytest]> exit
      
      

      Attachments

        Activity

          People

            tntnatbry Gagan Goel (Inactive)
            dleeyh Daniel Lee (Inactive)
            Roman Roman
            Daniel Lee Daniel Lee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.