Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
With the implementation of (for example) MDEV-5271 we can now add ENGINE specific attributes to individual partitions.
However, the number of ENGINE specific attributes is currently limited. For example, for InnoDB we have (only):
ha_create_table_option innodb_table_option_list[]=
|
{
|
/* With this option user can enable page compression feature for the |
table */
|
HA_TOPTION_SYSVAR("PAGE_COMPRESSED", page_compressed, compression_default), |
/* With this option user can set zip compression level for page |
compression for this table*/
|
HA_TOPTION_NUMBER("PAGE_COMPRESSION_LEVEL", page_compression_level, 0, 1, 9, 1), |
/* With this option the user can enable encryption for the table */ |
HA_TOPTION_ENUM("ENCRYPTED", encryption, "DEFAULT,YES,NO", 0), |
/* With this option the user defines the key identifier using for the encryption */ |
HA_TOPTION_SYSVAR("ENCRYPTION_KEY_ID", encryption_key_id, default_encryption_key_id), |
 |
HA_TOPTION_END
|
};
|
Other storage engines can be evaluated for individual available attributes by checking ha_create_table_option for the engine.
Some (other) attributes were added before support for engine-defined attributes was implemented,, so they were done in the server.
There are however many more attributes, currently implemented at the server level, which may be of interest. See for example https://mariadb.com/kb/en/create-table/#table-options
This feature request to move all such attributes to the storage engine level.
Attachments
Issue Links
- relates to
-
MDEV-22168 Supporting multiple engines with table partitioning
- Stalled
-
MDEV-5271 Support engine-defined attributes per partition
- Closed
-
MDEV-27564 Clearly specify/indicate in the partitioning manual which per-partition options are available
- Confirmed