Bug #94697 Partition error message bug when upgrading in place from mysql 5.7 to 8.0

• Submitted: 19 Mar 2019 8:09
• Modified: 10 May 2019 5:21
• Reporter: Masashi Hachuda
• Status: Duplicate
• Category: MySQL Server: Logging
• Severity: S3 (Non-critical)
• Version: 8.0.15
• OS: CentOS (CentOS Linux release 7.6.1810)
• CPU Architecture: x86 (x86_64)

[19 Mar 2019 8:09] Masashi Hachuda

Description:
I replaced the 5.7 binary with the 8.0 binary and started the 'mysql server' for an in-place upgrade from 5.7 to 8.0.

The instance uses MyISAM as the partition's storage engine.

Then I got the following error message:
`The 'partitioning' feature is not available; you need to remove '--skip-partition' or use MySQL built with '-DWITH_PARTITION_STORAGE_ENGINE=1'`

We can not solve this error by following the error message.

i knew this.
> To prepare for migration to MySQL 8.0, any table with nonnative partitioning should be changed to use an engine that provides native partitioning, or be made nonpartitioned.

However, it was reported as wrong as an error message.

How to repeat:
1) Build a mysql 5.7 DB instance and create a table using MyISAM with a partitioned storage engine.

2) Switch boot binary 8.0 and boot.

Suggested fix:
I expect the following message:

> any table with nonnative partitioning should be changed to use an engine that provides native partitioning, or be made nonpartitioned.

This message is in the official documentation for mysql 5.7.
https://dev.mysql.com/doc/refman/5.7/en/partitioning.html

[19 Mar 2019 8:14] Masashi Hachuda

Change message to details

[19 Mar 2019 9:57] MySQL Verification Team

Hello Masashi,

Thank you for the report and feedback.

regards,
Umesh

[10 May 2019 5:21] Erlend Dahl

Duplicate of

Bug#94518 Wrong error message when upgrade from 5.7 sees a non-natively partitioned table