I don't see what kind of patch can help here. Perhaps the only solution is to edit the dump, adding at the beginning

DROP TABLE IF EXISTS `mysql`.`global_priv`;

DROP VIEW IF EXISTS `mysql`.`user`;

I tried the above for upgrade from 10.1/10.2/10.3 to 10.4, it appears to be working.

An alternative, maybe somewhat more user-friendly, option could be running mysqldump with --add-drop-database option. It will drop the entire mysql database, including the view in question. I suppose if users restore the entire schemata, including system tables, it should be acceptable.
Of course it is only applicable if the users are creating dumps now. If they already have the dumps which they now need to restore, editing the dump is the only option we can think of.

What about to adjust mysqldump in next releases of MariaDB 10.2 and 10.3 so it automatically adds "DROP VIEW IF EXISTS `user`" statement? That would help users that will create a dump and migrate from MariaDB 10.2/3 to 10.4 in the future. The rest of them, who already created the dump, will have to add this line manually, obviously. Still, it can help a lot of users. Does this solution make a sense to you?

Yes, it does. We can do that. But as elenst noted above, mysqldump --add-drop-database already works, it's existing documented and future-proof option. Wouldn't it be a preferred solution compared to adding drops just for the case a user might want to dump in 10.2 and load in 10.4?

From my point of view, adding drops to mysqldump for 10.2 and 10.3 is a foolproof solution and it would prevent us from getting a lot of bug reports where the answer would be always "just use --add-drop-database option" or "alter your dump file please". I think it's easier and smoother to patch it than try to deliver this information to all migrating users.

Can you please let me know if you decided to fix it? Thanks!

okay, let's do it

Hello Sergei, what's the status of this issue, please?

it's assigned to a developer to be fixed. in 10.1, 10.2, 10.3

--add-drop-database is affected by https://bugs.mysql.com/bug.php?id=69970

Hi there, is there any update on this issue?

MDEV-23630 has added a new option, --system=all/users/.... In this mode mysqldump will use CREATE USER and GRANT statements instead of INSERT, so it'll work for any MariaDB version.

mysqldump --system=all does not work on an already initialized database so I think that's not really usable. A dump created with this option also create the user root@localhost that has already been added by mysql_install_db.