Bug #83275 Upgrade to 8.0.1 from 5.7 fails in SP PARSING
Submitted: 5 Oct 2016 22:49 Modified: 17 Nov 2016 16:46
Reporter: Abhishek Ranjan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:8.0.1 OS:Any
Assigned to: CPU Architecture:Any

[5 Oct 2016 22:49] Abhishek Ranjan
Description:
Upgrade to 8.0.1 aborts if server gets an error in parsing a SP created in mysql-5.7.

How to repeat:
1. Initialize and 5.7 server.
2. Execute following statements.

   create schema test;
   use test;
   delimiter |
   create procedure proc1(out a int) begin select requesting_trx_id from information_schema.INNODB_LOCK_WAITS limit 1 into a; end|
   delimiter ;

3. shutdown 5.7 server.
4. Start 8.0.1 server on same data directory.

Suggested fix:
Log the parsing error in error log. Do not abort upgrade.
[17 Nov 2016 16:46] Paul DuBois
Posted by developer:
 
Noted in 8.0.1 changelog.

An in-placed upgrade from MySQL 5.7 to MySQL 8.0 failed if parsing of
a stored routine body failed while migrating the routine. Now a
warning is reported and the routine is created without parsing its
body. Also, warnings are now reported when dependency resolution
fails for a view during view migration.