Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug][Dashboard] The whitelist input format of binlog source need to be optimized #5122

Closed
1 of 2 tasks
bruceneenhl opened this issue Jul 19, 2022 · 2 comments · Fixed by #5838
Closed
1 of 2 tasks
Assignees
Labels
Milestone

Comments

@bruceneenhl
Copy link
Contributor

bruceneenhl commented Jul 19, 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?

  • Yes, I am willing to submit a PR!

Code of Conduct

@bruceneenhl bruceneenhl added the type/bug Something is wrong label Jul 19, 2022
@leezng 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 healchow added this to the 1.4.0 milestone Sep 6, 2022
@healchow 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
@healchow
Copy link
Member

healchow commented Sep 8, 2022

After confirmation, the Debezium engine used in the Agent will take the intersection of the database name whitelist and the table name whitelist.

In order to facilitate user understanding and configuration, it is recommended to only open the configuration of the table name whitelist.

This means that the databaseWhiteList field needs to be removed in the dashboard module, leaving only the tableWhiteList parameter.

@healchow
Copy link
Member

healchow commented Sep 8, 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.

Chinese:

白名单应该是一个以逗号分隔的正则表达式列表,与要监控的表的完全限定名称相匹配。表的完全限定名称的格式为 <dbName>.<tableName>,其中 dbName 和 tablename 都可以配置正则表达式。
比如:test_db.table*,inlong_db*.user*,表示采集 test_db 库中以 table 开头的所有表 + 以 inlong_db 开头的所有库下的以 user 开头的所有表。

@healchow 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
@healchow healchow assigned leezng and unassigned healchow Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants