[MDEV-11426] Remove InnoDB INFORMATION_SCHEMA.FILES implementation Created: 2016-11-30  Updated: 2022-03-11  Due: 2016-12-01  Resolved: 2016-12-01

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.2.3

Type: Task Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: information_schema, innodb, tablespace

Issue Links:
Relates
relates to MDEV-19294 Remove TABLESPACE-related commands Closed
relates to MDEV-27886 innodb temporay tablespace files are ... Closed
relates to MDEV-19293 Remove information_schema.TABLESPACES Open
Sprint: 10.1.20

 Description   

MySQL 5.7 introduced WL#7943: InnoDB: Implement Information_Schema.Files to provide a long-term alternative for accessing tablespace metadata. The INFORMATION_SCHEMA.INNODB_* views are considered internal interfaces that are subject to change or removal between releases. So, users should refer to I_S.FILES instead of I_S.INNODB_SYS_TABLESPACES to fetch metadata about CREATE TABLESPACE.

Because MariaDB 10.2 does not support CREATE TABLESPACE or CREATE TABLE…TABLESPACE for InnoDB, it does not make sense to support I_S.FILES either. So, let MariaDB 10.2 omit the code that was added in MySQL 5.7. After this change, I_S.FILES will report the empty result, unless some other storage engine in MariaDB 10.2 implements the interface. (This interface was originally created for the NDB Cluster.)



 Comments   
Comment by Marko Mäkelä [ 2016-12-01 ]

While doing this, I also fixed some broken (skipped or disabled) tests in --suite=innodb_zip. I imported some missing .inc files from MySQL 5.7.

Comment by Jan Lindström (Inactive) [ 2016-12-01 ]

Looks correct to me and good that we have those innodb_zip suite test back there.

Comment by Marco Marsala [ 2019-09-23 ]

It also fixes a security issue related tothis table

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