Sync-diff-inspector configuration not effective

Translated
1

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

Original topic: sync-diff-inspector配置不生效

| username: 孤君888

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
[Reproduction Path] What operations were performed to cause the issue
[Encountered Issue: Problem Phenomenon and Impact]

My upstream is TIDB 6.1, downstream is MYSQL PerconaServer 5.7, and I set to ignore JSON in sync-diff-inspector, but it doesn’t seem to work? My sync-diff-inspector configuration is as follows:

# Diff Configuration.

######################### Global config #########################

check-thread-count = 4

export-fix-sql = true

check-struct-only = false


######################### Datasource config #########################
[data-sources]
[data-sources.tidb1]
    host = "10.x.x.x"
    port = 4000
    user = "xxx"
    password = "xxx"


[data-sources.mysql1]
    host = "10.x.x.x"
    port = 3308
    user = "xxx"
    password = "xxx"


########################### Routes ###########################

######################### Task config #########################

[task]

    output-dir = "./output"

    source-instances = ["tidb1"]

    target-instance = "mysql1"

    target-check-tables = ["db1.*", "test.*" ]

    target-configs = ["config1"]

######################### Table config #########################

[table-configs.config1]

  target-tables = ["db1.*"]
  ignore-columns = ["json","bit","blob"]

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: WalterWj | Original post link

Some versions calculate the result of the XOR operation on JSON formatted fields incorrectly, so they need to be skipped.

You can try not skipping them first.

3
| username: 孤君888 | Original post link

I have already configured ignore-columns, and JSON has also been ignored, but the logs in the actual output directory still warn about finding inconsistent rows. I checked these inconsistent rows, and the data in the JSON type fields are different, while the other fields are normal.

4
| username: 我是咖啡哥 | Original post link

The configuration here should be column names, not field types.

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.