InnoDB bloats the error_log and windows event logs with Notes when performing manual InnoDB file-per-table tablespace import

Recently, I’ve been trying to push for our production servers to be updated to a more recent version of MariaDB. We are currently using version 10.6.10, and I would like to update our servers to 11.4.4 due to performance improvements introduced in newer versions. However, during testing I’ve encountered an issue with the error_log and how it sends all logged events to the Windows Event Logs.

I’ve attached a portion of the error_log (named log_error.7z) below (the full file is around 15 GB due to this issue), as well as the configuration file I am using during testing. I am also attaching a zipped folder (simulation_scenario.7z) containing a table with fictional data and an instructions .txt file detailing the commands I ran during testing. You will notice that after the import finishes its process the error_log becomes filled with lines similar to the ones that showed up in the log mentioned before, a wall of text composed of "[Note] InnoDB: trying to read page [page id: space=11857, page number=100] in non existing or being-dropped tablespace" multiple times per second.

I am using both note_verbosity="" and log_warnings=1, as I understood they should reduce the amount of unnecessary output in log_error. The tests, however, showed that they have no effect in this case. Because of that, I believe it would be ideal for note_verbosity to begin suppressing these messages or for a new variable to be added to disable them.