CREATE TABLE Statement to  .MYI  files for tables created with no  INDEX DIRECTORY  option. To suppress this behavior, start the server with the  --keep_files_on_create  option, in which case  MyISAM  does not overwrite existing files and returns an error instead. If a  MyISAM  table is created with a  DATA DIRECTORY  or  INDEX DIRECTORY  option and an existing .MYD  or  .MYI  file is found,  MyISAM  always returns an error, and does not overwrite a file in the specified directory. Important You cannot use path names that contain the MySQL data directory with  DATA DIRECTORY  or  INDEX DIRECTORY . This includes partitioned tables and individual table partitions. (See Bug #32167.) • DELAY_KEY_WRITE Set this to 1 if you want to delay key updates for the table until the table is closed. See the description of the  delay_key_write  system variable in Section 5.1.8, “Server System Variables” . ( MyISAM  only.) • ENCRYPTION The  ENCRYPTION  clause enables or disables page-level data encryption for an  InnoDB  table. A keyring plugin must be installed and configured before encryption can be enabled. Prior to MySQL 8.0.16, the ENCRYPTION  clause can only be specified when creating a table in an a file-per-table tablespace. As of MySQL 8.0.16, the  ENCRYPTION  clause can also be specified when creating a table in a general tablespace. As of MySQL 8.0.16, a table inherits the default schema encryption if an  ENCRYPTION  clause is not specified. If the  table_encryption_privilege_check  variable is enabled, the TABLE_ENCRYPTION_ADMIN  privilege is required to create a table with an  ENCRYPTION  clause setting that differs from the default schema encryption. When creating a table in a general tablespace, table and tablespace encryption must match. As of MySQL 8.0.16, specifying an  ENCRYPTION  clause with a value other than  ’N’  or  ’’  is not permitted when using a storage engine that does not support encryption. Previously, the clause was accepted. For more information, see Section 15.13, “InnoDB Data-at-Rest Encryption” . • ENGINE_ATTRIBUTE  and  SECONDARY_ENGINE_ATTRIBUTE  options (available as of MySQL 8.0.21) are used to specify table attributes for primary and secondary storage engines. The options are reserved for future use. Permitted values are a string literal containing a valid  JSON  document or an empty string (’’). Invalid JSON  is rejected. CREATE TABLE t1 (c1 INT) ENGINE_ATTRIBUTE=’{" key ":" value "}’; ENGINE_ATTRIBUTE  and  SECONDARY_ENGINE_ATTRIBUTE  values can be repeated without error. In this case, the last specified value is used. ENGINE_ATTRIBUTE  and  SECONDARY_ENGINE_ATTRIBUTE  values are not checked by the server, nor are they cleared when the table’s storage engine is changed. 2556