Incorrect 0 row(s) affected on delete

when I was doing some tests I observed that when I delete a row (via a join to another column store table) the server reports 0 rows affected even when row is deleted.

Here's a sample...

– version=10.2.10-MariaDB-log
– version_comment=Columnstore 1.1.2-1

CREATE TABLE cs1 (
id INT(10) UNSIGNED NOT NULL,
`timestamp_` DATETIME,
numeric_val DOUBLE DEFAULT NULL
) ENGINE=columnstore;
INSERT INTO cs1 VALUES (1, '2018-01-09 21:59:02', 11.11)

CREATE TABLE cs2 (
id INT(10) UNSIGNED NOT NULL,
`timestamp_` DATETIME,
numeric_val DOUBLE DEFAULT NULL
) ENGINE=columnstore;

INSERT INTO cs2 VALUES (1, '2018-01-09 21:59:02', 22.22);

SELECT * FROM cs1;
DELETE FROM cs1 WHERE id = 1;
– correctly reporting rows affected
– Query: delete from cs1 where id = 1
– 1 row(s) affected
SELECT * FROM cs1;
– Query: select * from cs1 LIMIT 0, 5000
– 0 row(s) affected

INSERT INTO cs1 VALUES (1, '2018-01-09 21:59:02', 11.11);

SELECT * FROM cs1;
SELECT * FROM cs2;
DELETE cs1 FROM cs1
JOIN cs2 USING(id,timestamp_);
– reporting 0 rows affected when 1 row was affected
– Query: DELETE cs1 from cs1 join cs2 using(id,timestamp_)
– 0 row(s) affected

SELECT * FROM cs1;
– Query: SELECT * FROM cs1 LIMIT 0, 5000
– 0 row(s) affected

SELECT * FROM cs2;
– Query: SELECT * FROM cs2 LIMIT 0, 5000
– 1 row(s) affected