[MCOL-1692] Change engine in function from columnstore_info from MyISAM to Aria Created: 2018-09-04  Updated: 2020-04-01  Resolved: 2018-09-04

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: 1.0.0
Fix Version/s: Icebox

Type: Task Priority: Minor
Reporter: Richard Stracke Assignee: Andrew Hutchings (Inactive)
Resolution: Done Votes: 0
Labels: None
Environment:

discovered on Debian 9, MCS 1.1.5


 Description   

The function

columnstore_info.table_usage creates 2 MyISAM tables in the database Columnstore_info,
which will be dropped after the function is finished.

columnstore_info.columnstore_columns;
columnstore_info.columnstore_files;

The create table code use explicit MyISAM
"engine=MyISAM"

    CREATE TABLE columnstore_info.columnstore_columns engine=MyISAM as (select * from information_schema.columnstore_columns);
 
[...]
 
    CREATE TABLE columnstore_info.columnstore_files engine=MyISAM as (select * from information_schema.columnstore_files);

Should be changed to aria

    CREATE TABLE columnstore_info.columnstore_columns engine=aria as (select * from information_schema.columnstore_columns);
 
[...]
 
    CREATE TABLE columnstore_info.columnstore_files engine=aria as (select * from information_schema.columnstore_files);



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2018-09-04 ]

This has already been completely changed for 1.1.6. We now have condition pushdown in the I_S tables to accelerate them, the table_usage function has been completely re-factored and the only create table now is:

CREATE TEMPORARY TABLE columnstore_info.columnstore_files (TABLE_SCHEMA VARCHAR(64), TABLE_NAME VARCHAR(64), DATA BIGINT, DICT BIGINT);

This makes it dependent on MariaDB server which engine to use.

Generated at Thu Feb 08 02:30:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.