[MCOL-3694] TIMESTAMP data type is accepted but causes invalid (unsupported) data structure, mysqldump fails Created: 2019-12-25  Updated: 2023-10-25  Resolved: 2023-10-25

Status: Closed
Project: MariaDB ColumnStore
Component/s: PrimProc
Affects Version/s: 1.4.2, 1.5.3
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Leonid Fedorov
Resolution: Done Votes: 2
Labels: None

Issue Links:
Relates
relates to MCOL-265 TIMESTAMP data type not supported Closed
relates to MCOL-1039 DATE / DATETIME should support CURREN... Closed

 Description   

The problem is caused by a combination of fixed MCOL-265 (support for TIMESTAMP) and unfixed MCOL-1039 (support for CURRENT_TIMESTAMP).

drop table if exists t1;
 
create table t1 (a timestamp) engine=Columnstore;
 
show create table t1;

By default, TIMESTAMP column in MariaDB server has CURRENT_TIMESTAMP as default/on update value. So, the resulting table is

CREATE TABLE `t1` (
 
  `a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
 
) ENGINE=Columnstore DEFAULT CHARSET=latin1

However, since current_timestamp is not supported for Columnstore, this statement cannot be run:

MariaDB [db]> CREATE TABLE `t1` (
 
    ->   `a` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
 
    -> ) ENGINE=Columnstore DEFAULT CHARSET=latin1
 
    -> ;
 
ERROR 1178 (42000): The storage engine for the table doesn't support The syntax or the data type(s) is not supported by Columnstore. Please check the Columnstore syntax guide for supported syntax or data types.

It means that tools which rely on the output of SHOW CREATE TABLE – importantly, mysqldump, but there might be others – will fail as long as there is at least one such table.
Generated at Thu Feb 08 02:44:44 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.