dumpling导出不存在的表问题

【 TiDB 使用环境】
线上

【概述】 场景 + 问题概述
今天使用dumpling在导出数据的时候,由于把表名写错了,在使用dumpling导出的时候尽然没有报错,反而成功了
如下所示:
[root@hb30-dbs-scoredb-backup-124-244 ads_rt]# dumpling -h 10.30. -P xxxx -uxxxx -pxxxxx --filetype sql -t 8 -F 64MiB -B xxxx -T xxxx.obs_game_offline_server_10005 -o /data/test
Release version: v5.0.3
Git commit hash: 95099237b7beb80f66efaac9f3e02bd01e68bcc2
Git branch: heads/refs/tags/v5.0.3
Build timestamp: 2021-06-28 10:04:36Z
Go version: go version go1.13 linux/amd64

[2021/10/13 17:34:29.104 +08:00] [INFO] [versions.go:55] [“Welcome to dumpling”] [“Release Version”=v5.0.3] [“Git Commit Hash”=95099237b7beb80f66efaac9f3e02bd01e68bcc2] [“Git Branch”=heads/refs/tags/v5.0.3] [“Build timestamp”=“2021-06-28 10:04:36”] [“Go Version”=“go version go1.13 linux/amd64”]
[2021/10/13 17:34:29.107 +08:00] [INFO] [config.go:600] [“detect server type”] [type=MySQL]
[2021/10/13 17:34:29.107 +08:00] [INFO] [config.go:619] [“detect server version”] [version=5.7.16-10-log]
[2021/10/13 17:34:29.107 +08:00] [INFO] [dump.go:83] [“begin to run Dump”] [conf="{“s3”:{“endpoint”:"",“region”:"",“storage-class”:"",“sse”:"",“sse-kms-key-id”:"",“acl”:"",“access-key”:"",“secret-access-key”:"",“provider”:"",“force-path-style”:true,“use-accelerate-endpoint”:false},“gcs”:{“endpoint”:"",“storage-class”:"",“predefined-acl”:"",“credentials-file”:""},“AllowCleartextPasswords”:false,“SortByPk”:true,“NoViews”:true,“NoHeader”:false,“NoSchemas”:false,“NoData”:false,“CompleteInsert”:false,“TransactionalConsistency”:true,“EscapeBackslash”:true,“DumpEmptyDatabase”:true,“PosAfterConnect”:false,“CompressType”:0,“Host”:“10.30.124.235”,“Port”:4306,“Threads”:8,“User”:“dba_admin”,“Security”:{“CAPath”:"",“CertPath”:"",“KeyPath”:""},“LogLevel”:“info”,“LogFile”:"",“LogFormat”:“text”,“OutputDirPath”:"/data/hotfix/ads_rt",“StatusAddr”:":8281",“Snapshot”:"",“Consistency”:“flush”,“CsvNullValue”:"\\N",“SQL”:"",“CsvSeparator”:",",“CsvDelimiter”:"\"",“Databases”:[“zzzz”],“Where”:"",“FileType”:“sql”,“ServerInfo”:{“HasTiKV”:false,“ServerType”:1,“ServerVersion”:“5.7.16-10-log”},“Rows”:0,“ReadTimeout”:900000000000,“TiDBMemQuotaQuery”:0,“FileSize”:67108864,“StatementSize”:1000000,“SessionParams”:{},“Tables”:null}"]
[2021/10/13 17:34:29.274 +08:00] [INFO] [dump.go:178] [“All the dumping transactions have started. Start to unlock tables”]
[2021/10/13 17:34:29.275 +08:00] [INFO] [collector.go:212] [“backup Success summary: total backup ranges: 1, total success: 1, total failed: 0, total take(backup time): 691.936µs, total take(real time): 720.744µs”]
[2021/10/13 17:34:29.275 +08:00] [INFO] [main.go:81] [“dump data successfully, dumpling will exit now”]

导出的结果只有建库的sql文件和metadata文件

ll

total 8
-rw-r–r-- 1 root root 94 Oct 13 17:34 xxxx-schema-create.sql
-rw-r–r-- 1 root root 405 Oct 13 17:34 metadata

没有报错,成功了,这种表不存在,不应该报错提示表不存在吗?感觉不合理呀

dumpling 是在 mydumper 基础上重构的,这个行为跟 mydumper 是一致的
https://github.com/maxbube/mydumper ,可以认为这里忽略了不存在的表