[MCOL-5538] calshowpartitionsbyvalue() failed on tables with utf8 charset and collation Created: 2023-07-21  Updated: 2023-10-27  Resolved: 2023-10-27

Status: Closed
Project: MariaDB ColumnStore
Component/s: PrimProc
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Leonid Fedorov
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

Build tested: develop branch

This issue is discovered while testing MCOL-5519, which sets the following in the columnstore.cnf file.

collation_server = utf8_general_ci
character_set_server = utf8

The following development regression test case failed:

working_tpch1_compareLogOnly/misc/bug4594.sql

MariaDB [tpch1]> create table if not exists bug4594(c1 char(5))engine=columnstore;
Query OK, 0 rows affected (0.330 sec)
 
MariaDB [tpch1]> insert into bug4594 values ('abc'), ('def');
Query OK, 2 rows affected (0.313 sec)
Records: 2  Duplicates: 0  Warnings: 0
 
MariaDB [tpch1]> select * from bug4594;
+------+
| c1   |
+------+
| abc  |
| def  |
+------+
2 rows in set (0.044 sec)
 
MariaDB [tpch1]> select calshowpartitionsbyvalue('bug4594', 'c1', 'aa', 'zz') into @y;
ERROR 1815 (HY000): Internal error: MCS-1016: The column type CHAR(15) is currently  not supported in calShowPartitionsByValue function.

The same test case worked fine when charset and collation are set to latin1.



 Comments   
Comment by Daniel Lee (Inactive) [ 2023-07-21 ]

test case working_tpch1_calpontonly/misc/calShowPartitionsByValue.sql also failed.

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