[MDEV-18215] mariabackup does not report unknown command line options Created: 2019-01-11 Updated: 2023-09-26 Resolved: 2020-06-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Backup, mariabackup, Scripts & Clients |
| Affects Version/s: | 10.1.37, 10.2.21, 10.3.12 |
| Fix Version/s: | 10.5.4, 10.4.14 |
| Type: | Bug | Priority: | Major |
| Reporter: | Hartmut Holzgraefe | Assignee: | Vladislav Lesin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
E.g. '--no-such-option raises neither an error nor a warning:
This is especially a problem when trying to use an option that was only added in a later version. |
| Comments |
| Comment by Geoff Montee (Inactive) [ 2019-01-11 ] |
|
I added a note about this here: https://mariadb.com/kb/en/library/mariabackup-overview/ |
| Comment by Ulrich Moser (Inactive) [ 2020-04-23 ] |
|
Not only does mariabackup not complain about unknown options but shows unpredectable behaviour (see |
| Comment by Hartmut Holzgraefe [ 2020-04-23 ] |
|
The behavior isn't really unpredictable, it is actually perfectly deterministic. But I agree that this makes typos way too dangerous, and that this behavior is like running with scissors, or like juggling running chain saws ... The problem is in the "everything that is not a mariabackup option by itself gets passed on to the embedded server instance" approach, where on that level the server option parsing code does not know about the mariabackup specific options. So in both option parsing steps we get to "i don't understand this, but probably the other option parser might, so i can't complain about not understanding this specific parameter" behavior. So no easy fix here, but I'd not only consider this problem "major", but even "critical" at this point ... |