[MCOL-725] ERROR 1118 (42000): Row size too large... within SELECT statement. Created: 2017-05-23  Updated: 2017-05-23  Resolved: 2017-05-23

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: 1.0.9
Fix Version/s: Icebox

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

AWS CentOS 7

Issue Links:
Duplicate
duplicates MCOL-713 Some functions return "The maximum ro... Closed

 Description   

The maximum of all selected fields within the SELECT statement has a limit in 65535 bytes. It is not a common ERROR 1118 (42000), it is not file format related and can't be reproduced on the regular MariaDB with the same InnoDB_version. It seems that you materialize the SELECT output into TEMP table or something like this, not sure.

The issue can be easily reproduced in following ways:

1. 

select * from (select cast(123 AS CHAR(21845)) as f,cast(123 AS CHAR(21845)) as g,cast(123 AS CHAR(21845)) as h) m1;

2. 

CREATE TABLE `t1` (
 
  `c1` varchar(32765) NOT NULL,
 
  `c2` varchar(32766) NOT NULL
 
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 
 
insert into t1 select '123','123';
 
 
 
select c1,c2,c1 from t1;
 
 
 
ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

The same perfectly works on 10.1.22-MariaDB.

 Comments   
Comment by Andrew Hutchings (Inactive) [ 2017-05-23 ]

This is a duplicate of MCOL-713. It is a side-effect of the InfiniDB/ColumnStore 1.0 workaround to make ORDER BY work. Basically we hard-set the maximum string length before conversion to TEXT type internally in MariaDB to 65535. By default UTF-8 (3 byte fixed allocation) is used so the maximum row length of UTF-8 text will be 21845, so 3x7281 chars for your example. The only real workaround for now would be to increase the char to 65535.

Once MCOL-643 is resolved in 1.1 we can then resolve MCOL-713 very easily.

It will be fixed in ColumnStore 1.1.

Comment by Andrew Hutchings (Inactive) [ 2017-05-23 ]

Closed as duplicate of MCOL-713

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