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

Not all data escaped when inserting with select statement from innodb table into columnstore

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.0.9, 1.0.10
    • 1.0.12, 1.1.1
    • cpimport, DMLProc
    • None
    • Centos 7
    • 2017-18, 2017-19, 2017-20, 2017-21

    Description

      It seems that however cpimport imports data from a select insert is having trouble when the table has at least 2 fields with more than one backslash (and ending with a backslash). The error can be reproduced with the SQL below:

      CREATE TABLE IF NOT EXISTS data.example_columnstore_table (  
            `Blah` VARCHAR(255) NOT NULL      
      ) ENGINE=columnstore;
       
      CREATE TABLE IF NOT EXISTS data.example_innodb_table (  
            `Blah` VARCHAR(255) NOT NULL      
      ) ENGINE=INNODB;
       
      INSERT INTO data.example_innodb_table (`Blah`) VALUES ("test \ ing \\");
      INSERT INTO data.example_innodb_table (`Blah`) VALUES ("foo");
      INSERT INTO data.example_innodb_table (`Blah`) VALUES ("test \ ing \\");
      INSERT INTO data.example_columnstore_table (`Blah`) SELECT `Blah` FROM data.example_innodb_table;
      

      It looks like the last value isn't properly escaped and so expects more data to be inserted, but that may be a misunderstanding of what it's doing on my part. Either way, it fails and locks the table.

      Attachments

        Issue Links

          Activity

            People

              dleeyh Daniel Lee (Inactive)
              mattminix Matthew Minix
              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.