{"push_id":909034378,"size":1,"distinct_size":1,"ref":"refs/heads/ps-5.6-DB-720","head":"1cf79997605c9c06da87d32bbd034c288d20e3ee","before":"081c59211e8d2ae6a6f44c90016af684940b74b3","commits":[{"sha":"1cf79997605c9c06da87d32bbd034c288d20e3ee","author":{"email":"cffc851ded781682acb7242e4f68ec50560e83e2@percona.com","name":"George O. Lorch III"},"message":"https://bugs.launchpad.net/percona-server/+bug/1527730\nDB-720 : ps 5.6 Can not create a clustering index on a partitioned tokudb table\nDuring an attempt to create a clustering key, Percona Server has an extra check where it queries the storage engine handlerton to see if it supports clustered keys.\nWhen a partitioned table is in use, the partition storage engine is answering this query rather than the TokuDB storage engine.\n\nWe have to consider that even though Percona Server does not currently support a mixed set of storage engines for partitions, there is much code that is built around that possibility.\n\nThis fix adds the HTON_SUPPORTS_CLUSTERED_KEYS flag to the partition handlerton to indicate that it _could_ support clustered keys if all of the underlying handlertons do.\n\n\"mysql_prepare_create_table\" has been changed to enumerate and all partitions if they exist ant test each partitions real handlerton for the HTON_SUPPORTS_CLUSTERED_KEYS\n\nRemoved some vestigial TokuDB handler method.\n\nFactored out common cluster_key tests from tokudb.cluster_key into suite/tokudb/include/cluster_key.inc\n\nChanged the tokudb.cluster_key test to include the newly factored out test case.\n\nRe-enabled the tokudb.cluster_key_part test and added several tests to it to validate grammar functionality and use factored cluster_key tests to ensure that clustered keys are in fact being chosen by the optimizer through the partition engine.\n\nUpdated the main.tokudb_clustering_key_grammar to include some partitioning grammar tests.","distinct":true,"url":"https://api.github.com/repos/georgelorchpercona/percona-server/commits/1cf79997605c9c06da87d32bbd034c288d20e3ee"}]}