Bug #98416 Please provide better upgrade/startup incompatibility issues?
Submitted: 28 Jan 2020 15:20 Modified: 30 Jan 2020 14:59
Reporter: Simon Mudd (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Installing Severity:S4 (Feature request)
Version:8.0.18 OS:Any
Assigned to: CPU Architecture:Any
Tags: startup, upgrade, view_issue

[28 Jan 2020 15:20] Simon Mudd
Description:
Error reporting when starting a 8.0 server (upgrading from 5.7) shows the following:

2020-01-28T15:12:28.282688Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'db.view1' failed. View is no more valid to use
2020-01-28T15:12:28.283874Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'db.view2' failed. View is no more valid to use
2020-01-28T15:12:28.284943Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'db.view3' failed. View is no more valid to use
2020-01-28T15:12:28.286112Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'db.view4' failed. View is no more valid to use
2020-01-28T15:12:32.561329Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'db.view5' failed. View is no more valid to use
2020-01-28T15:12:32.562777Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'db.view6' failed. View is no more valid to use

How to repeat:
Find a box that has some sort of issue with its view. (I found this one)
Upgrade from 5.7.2X to 8.0.18

See the error message reported.

Suggested fix:
Provide a better, more complete error message to indicate WHAT the problem is. It's good to know there is a problem but it would be MUCH better to know what the problem is.

* context?
* SQL issue?
* missing underlying tables?
....

I can imagine why there's a problem here but I think the logging should give a better indication of what is wrong.

I'm not desperately worried about this but I do think it would help enormously given mysqld is complaining something is wrong to expose more details than are currently being shown.

Also the English is not that good. It would be helpful to change this to something like View is no longer valid (so it was valid before???) or Invalid view: <reason for invalidity>
[30 Jan 2020 14:59] MySQL Verification Team
Hello Simon,

Thank you for your feature request.

I have encountered similar problems. I agree that we can provide more verbose errors in this case.

Verified as a feature request.
[30 Jan 2020 15:00] MySQL Verification Team
One more small item.

If you could provide CREATE VIEW statement, for any of the above views, it would be helpful.

You can provide it in the hidden message.