You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
leezng
changed the title
[Bug][Dashboard] The whitelist input format of binlog source need to be optimized.
[Bug][Dashboard][Manager] The whitelist input format of binlog source need to be optimized.
Aug 22, 2022
healchow
changed the title
[Bug][Dashboard][Manager] The whitelist input format of binlog source need to be optimized.
[Bug][Dashboard][Manager] The whitelist input format of binlog source need to be optimized
Sep 7, 2022
At the same time, for ease of understanding, it is recommended to add the following description:
English:
The whitelist should be a comma-separated list of regular expressions that match the fully-qualified names of tables to be monitored. Fully-qualified names for tables are of the form <databaseName>.<tableName>, the dbName and tableName can be configured with regular expressions.
For example, "test_db.order*, inlong_db*.user*", means to collect all tables starting with order in the test_db database + all tables starting with user under all databases starting with inlong_db.
healchow
changed the title
[Bug][Dashboard][Manager] The whitelist input format of binlog source need to be optimized
[Bug][Dashboard] The whitelist input format of binlog source need to be optimized
Sep 8, 2022
What happened
The correct input format is as follows:
#5050
What you expected to happen
Given the right input format, and some instructions about the format.
How to reproduce
Using whitelist
Environment
No response
InLong version
master
InLong Component
InLong Dashboard
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: