LP #1560702: MyISAM import results in empty query result
General
Escalation
General
Escalation
Description
**Reported in Launchpad by Donald Tripp last update 24-03-2016 03:24:45
Importing a database with existing MyISAM tables does not throw an error when imported into Percona InnoDB cluster, and works fine on the node it was imported into. Other nodes in the cluster return empty result sets for any query. This behavior is confusing at first to many users, and takes some time to diagnose. Suggestion would be to throw an error when trying to import a MyISAM table into InnoDB cluster.
Environment
None
Smart Checklist
Activity
Show:
lpjirasync January 14, 2018 at 5:58 PM
**Comment from Launchpad by: Krunal Bauskar on: 24-03-2016 03:24:13
Ideally if user plan import MYISAM table and want them to be replicate further in cluster it is advisable to set wsrep_replicate_myisam=ON (but note that myisam support is experimental and can have issue)
It would be easier/advisable for end-user to control the import rules that are being defined by user for a tool that is either 3rd party tool or mysql native tool.
PXC raising warning/error for imported MyISAM table would further created confusion when user intend to import MyISAM tables. Also there are system tables those needs to be in MyISAM format. Raising error for these table would stall import process.
lpjirasync January 14, 2018 at 5:58 PM
**Comment from Launchpad by: Donald Tripp on: 22-03-2016 22:10:31
Version 5.6.24-72.2-56 on x64 and 5.6.27-76.0-56 on x64.
**Reported in Launchpad by Donald Tripp last update 24-03-2016 03:24:45
Importing a database with existing MyISAM tables does not throw an error when imported into Percona InnoDB cluster, and works fine on the node it was imported into. Other nodes in the cluster return empty result sets for any query. This behavior is confusing at first to many users, and takes some time to diagnose. Suggestion would be to throw an error when trying to import a MyISAM table into InnoDB cluster.