[MDEV-11381] AliSQL: [Feature] Issue#30 SUPPORT BIG COLUMN COMPRESS Created: 2016-11-29  Updated: 2017-08-31  Resolved: 2017-08-31

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: 10.3.2

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-11371 Big column compressed Closed
Epic Link: AliSQL patches

 Description   

New syntax:
-----------
column_definition:
   data_type [NOT NULL | NULL] [DEFAULT default_value]
   [AUTO_INCREMENT] [UNIQUE [KEY] | [PRIMARY] KEY]
   [COMMENT 'string']
   [COLUMN_FORMAT
   {FIXED|DYNAMIC|COMPRESSED|DEFAULT}]
   [STORAGE {DISK|MEMORY|DEFAULT}]
   [reference_definition]
 
Description:
------------
If the column was defined as a compressed column, then the column data will be
compressed using zlib. Currently blob/text/varchar/varbinary are supported.
 
DDL:
Currently Not allowed to define a index that include compressed
column, an error message throw(ER_BLOB_KEY_WITH_COMPRESS)
 
And use COPY algorithm if column_format was changed. So we can't use
online ddl to change the column format.
 
Control option:
innodb_rds_column_compression_level
innodb_rds_column_zip_threshold
innodb_rds_column_zlib_strategy
        These variables above are used to control the param for deflate used by
        column data compression.
innodb_rds_column_zip_threshold
        control the compress threshold, if the data length exceeds this value,
        then compress the data.

https://github.com/alibaba/AliSQL/commit/f9753b591202241cbd9d1a02c2d95e8ce6fdd1a1



 Comments   
Comment by Sergey Vojtovich [ 2017-08-31 ]

MariaDB has now slightly different implementation of column compression in 10.3: https://github.com/MariaDB/server/commit/fdc47792354c820aa4a8542d7c00d434424a63fb

Generated at Thu Feb 08 07:49:31 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.