Details
-
Task
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
Description
As noted in MDEV-11974, the InnoDB encryption that was introduced in MariaDB Server 10.1 is incompatible with the SPATIAL INDEX implementation of MySQL 5.7 that was merged into MariaDB Server 10.2.2.
MDEV-11974 was addressed by preventing or disabling the encryption of spatial indexes. For a later server release, we should come up with an encryption solution that works also on spatial indexes.
Attachments
Issue Links
- causes
-
MDEV-20383 Use of uninitialized value in Datafile::find_space_id() for ROW_FORMAT=COMPRESSED
-
- Closed
-
-
MDEV-23199 page_compression flag is missing for full_crc32 tablespace
-
- Closed
-
-
MDEV-23254 Replace FSP_FLAGS_HAS_PAGE_COMPRESSION with fil_space_t::is_compressed
-
- Closed
-
-
MDEV-26148 SEGV or Assertion `!page_is_comp(page) == !(index->table)->not_redundant()'
-
- Closed
-
- is caused by
-
MDEV-11974 Disable encryption of spatial indexes in MariaDB 10.2
-
- Closed
-
- relates to
-
MDEV-18097 Indicate which InnoDB data files are zero-initialized
-
- Closed
-
-
MDEV-18644 Support FULL_CRC32 for compressed pages.
-
- Closed
-
-
MDEV-19534 Make innodb_checksum_algorithm=full_crc32 by default, and remove innodb_checksums
-
- Closed
-
-
MDEV-21918 improve page_zip_verify_checksum()
-
- Closed
-
-
MDEV-32230 ROW_FORMAT column in I_S.INNODB_SYS_TABLESPACES is NULL for innodb_checksum_algorithm=full_crc32 tablespaces
-
- Closed
-
-
MDEV-21666 innodb_checksum_algorithm could use further clarification
-
- Closed
-
Activity
Transition | Time In Source Status | Execution Times |
---|
|
644d 3h 24m | 1 |
|
5d 19h 16m | 1 |
|
90d 22h 27m | 1 |
|
6h 22m | 1 |