Make sure utf8mb4 is supported in all contexts, like cpimport, INSERT ... SELECT, multiple table updates etc.

While we are on the topic, it would be great to have ALTER TABLE ... DEFAULT CHARSET = <new> also supported, same as changing CHARSET for individual columns.

Are these character sets not supported? ColumnStore doesn't complain if you try to use them:

MariaDB [db1]> CREATE TABLE utf8_tab (

    -> `id` int(11) DEFAULT NULL,

    -> `str` varchar(50) DEFAULT NULL

    -> ) ENGINE=Columnstore DEFAULT CHARSET=utf8;

Query OK, 0 rows affected (0.16 sec)

MariaDB [db1]> CREATE TABLE utf8mb4_tab (

    -> `id` int(11) DEFAULT NULL,

    -> `str` varchar(50) DEFAULT NULL

    -> ) ENGINE=Columnstore DEFAULT CHARSET=utf8mb4;

Query OK, 0 rows affected (0.16 sec)

MariaDB [db1]> SELECT @@global.version_comment;

+--------------------------+

| @@global.version_comment |

+--------------------------+

| Columnstore 1.1.6-1      |

+--------------------------+

1 row in set (0.00 sec)

Also, if these character sets are not supported, then why does the documentation say:

MariaDB Columnstore has the ability to support UTF-8 character sets.

https://mariadb.com/kb/en/library/mariadb-columnstore-system-usage/#configuring_to_use_utf-8_character_sets

toddstoffel and/or LinuxJedi,

Can you please clarify which specific features do not yet support utf8/utf8mb4? These character sets seem to work in a lot of different scenarios. And as I mentioned above, the ColumnStore documentation even has a section titled "Configuring to use UTF-8 Character sets".

Duplicated by the work done for MCOL-3536