[MCOL-910] ColumnStore SELECT causes implicit InnoDB commit Created: 2017-09-11  Updated: 2019-07-10  Resolved: 2019-07-10

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.0.11
Fix Version/s: Icebox

Type: Bug Priority: Minor
Reporter: Andrew Hutchings (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None


 Description   

When a ColumnStore query is executed it triggers an explicit commit for non-ColumnStore due to the internal vtable processing. Example:

CREATE TABLE `countries_innodb` (
  `code` varchar(255) NOT NULL
) ENGINE=InnoDB;
 
 
CREATE TABLE `countries_columnstore` (
  `code` varchar(255) NOT NULL
) ENGINE=ColumnStore;
 
 
INSERT INTO countries_innodb (code) VALUES ('BR');
 
 
BEGIN;
INSERT INTO countries_innodb (code) VALUES ('UK');
SELECT * from countries_columnstore;
ROLLBACK;
 
 
-- Result: two countries.
-- Expected: one country.
SELECT * FROM countries_innodb;



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2019-07-10 ]

We can't fix this < 1.4. Will go away in 1.4

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