TiCDC Configuration Field Selector Not Working

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiCDC配置字段选择器未生效

| username: TiDBer_E5BPfmPA

【TiDB Usage Environment】Production Environment
【TiCDC Version】v6.5.3
【Encountered Issue】After calling the CDC interface to create a task and configuring the field selector rule normally, Kafka can consume all field information in the table; no abnormal logs are printed.
“column_selectors”: [
{
“matcher”: [
“spk2.t8”
],
“columns”: [
“name”
]
}
【Task Configuration Information】
{
“upstream_id”: 7260705200573377846,
“namespace”: “default”,
“id”: “test104”,
“sink_uri”: “xxx”,
“create_time”: “2023-09-14T18:09:21.759953733+08:00”,
“start_ts”: 444251809176092674,
“config”: {
“memory_quota”: 1073741824,
“case_sensitive”: true,
“enable_old_value”: true,
“force_replicate”: false,
“ignore_ineligible_table”: false,
“check_gc_safe_point”: true,
“enable_sync_point”: false,
“bdr_mode”: false,
“sync_point_interval”: 600000000000,
“sync_point_retention”: 86400000000000,
“filter”: {
“do_tables”: [
{
“database_name”: “spk2”,
“table_name”: “t8”
}
],
“rules”: [
“spk2.t8”
]
},
“mounter”: {
“worker_num”: 16
},
“sink”: {
“protocol”: “canal-json”,
“schema_registry”: “”,
“csv”: {
“delimiter”: “,”,
“quote”: “”",
“null”: “\N”,
“include_commit_ts”: false,
“binary_encoding_method”: “”
},
“column_selectors”: [
{
“matcher”: [
“spk2.t8”
],
“columns”: [
“name”
]
}
],
“transaction_atomicity”: “”,
“encoder_concurrency”: 16,
“terminator”: “\r\n”,
“date_separator”: “day”,
“enable_partition_separator”: true,
“file_index_width”: 0,
“delete_only_output_handle_key_columns”: null
},
“consistent”: {
“level”: “none”,
“max_log_size”: 64,
“flush_interval”: 2000,
“use_file_backend”: false
},
“scheduler”: null,
“integrity”: null
},
“state”: “normal”,
“creator_version”: “v6.5.3”,
“resolved_ts”: 444251823685500930,
“checkpoint_ts”: 444251823685500930,
“checkpoint_time”: “2023-09-14 18:10:17.062”,
“task_status”: [
{
“capture_id”: “e50c4b63-ea20-4b2e-bc79-ab7053f08e32”,
“table_ids”: [
100
]
}
]
}
【Attachment: Screenshot】


| username: nongfushanquan | Original post link

The current version does indeed have this issue; this filtering feature has not been implemented in the system.

| username: ajin0514 | Original post link

Try a higher version.