Bug #94518 Wrong error message when upgrade from 5.7 sees a non-natively partitioned table
Submitted: 1 Mar 2019 8:38 Modified: 23 Mar 2019 14:22
Reporter: Sivert Sørumgård Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Data Dictionary Severity:S3 (Non-critical)
Version:8.0.17 OS:Any
Assigned to: CPU Architecture:Any

[1 Mar 2019 8:38] Sivert Sørumgård
5.7 supported non-native partitioning, 8.0 does not. When detecting a non-natively partitioned table during upgrade from 5.7, we issue the e error messageby calling: 

my_error(ER_FEATURE_NOT_AVAILABLE, MYF(0), "partitioning", "--skip-partition", "-DWITH_PARTITION_STORAGE_ENGINE=1");

This is misleading since we cannot build 8.0 with the partition engine at all.

How to repeat:
Start 5.7. Create a non-nativeky partitioned table. Upgrade to 8.0. Inspect error log.

Suggested fix:
[23 Mar 2019 14:22] Daniel Price
Posted by developer:
Fixed as of the upcoming 8.0.17 release, and here's the changelog entry:

An incorrect error message was reported during upgrade from MySQL 5.7 to
MySQL 8.0 when a non-natively partitioned table was encountered. The error
message referenced the -DWITH_PARTITION_STORAGE_ENGINE CMake build option,
which is not supported in MySQL 8.0.
[10 May 2019 5:20] Erlend Dahl
Bug#94697 Partition error message bug when upgrading in place from mysql 5.7 to 8.0

was marked as a duplicate.