[MCOL-489] Remove row size limitation of 65535 Created: 2016-12-29  Updated: 2017-12-01  Resolved: 2017-11-14

Status: Closed
Project: MariaDB ColumnStore
Component/s: MDB Plugin
Affects Version/s: None
Fix Version/s: 1.1.0

Type: New Feature Priority: Minor
Reporter: Zeng Chun Assignee: Andrew Hutchings (Inactive)
Resolution: Fixed Votes: 1
Labels: None


 Description   

Copied from the thread:
https://mariadb.com/kb/en/mariadb/mariadb-columnstore-can-we-extend-the-max-length-of-the-data-types-varchar-/

I think my use case is very common. We have a 1500 columns table where each row stores all the data of a single transaction. In order to create the table in the columnstore engine, we kept getting the error: "Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535"

The row size (and max number of columns of 4096) is a limit enforced by the mariadb server derived from the original mysql code base.

Two options:
1. Remove the row size limitation of 65535 so that we can create more columns to accommodate the content of Text/Blob data type. Frankly, I don't like this option for I have to split the content before inserting and concatenate them together before returning results.
2. Set high priority of supporting Text (MCOL-267) and Blob (MCOL-356) data types.

I set this issue as major priority for it will impact on the marketing of MariaDB ColumnStore. Thanks for your great support.



 Comments   
Comment by David Thompson (Inactive) [ 2016-12-30 ]

It is more likely that we'll support blob and text first and these will be tracked in the referenced tickets. The row size limitation is more of a fundamental limitation in mariadb server going all the way back to mysql. As such this is likely to be a fairly high effort.

Comment by Andrew Hutchings (Inactive) [ 2017-11-14 ]

Closing this as fixed in 1.1.0 since we now support BLOB/TEXT columns in 1.1.

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