Windows 11 22H2

While Mariabackup will take several innodb variables because it directly interacts with the database files directly, mysqldump.exe/mariadb-dump.exe purely interacts with the server via SQL and as such doesn't support any storage engine variables. All mysqldump.exe interactions with the server rely on the server settings.

Now understand the behavior why the messages occured,
but what people what is
"Okay sir, will fix it by ignore unsupported properties(and even display as ignored). Thanks" it is.
Be professional MaraDB guys. in attitude and product deliverable quality since it is kinda commercial product.

Hi Sir,

Ignoring incorrect options would be inconsistent with the existing handling of options server wide. An error provides the ability to correct a misspelling or understand why the option isn't there. If an ignore is required there is the --loose prefix that can apply to any option.

This will produce an ignored warning like:

$ client/mysqldump --loose-innodb_flush_method=unbuffered -S /tmp/build-mariadb-server-10.7-base.sock  --all-databases  > /dev/null

Warning: client/mysqldump: unknown variable 'loose-innodb_flush_method=unbuffered'

I see you've had a series of fairly serious bugs you have reported (much appreciated). As a former DBA I empathize with the pain this has caused.

I apologize if my standard of prompt responses falls short of your standards. I suspect the commercial support offering have staff that will offer a attitude you find more agreeable. I am trying to improve the quality with bug fixes (like MDEV-30492) to the reported problems, and/to identify systemic quality problems.

Appreciate for the reply. Truly.
(But pains still, as crashs as you know. Let people get out of here. Damn)