-
Notifications
You must be signed in to change notification settings - Fork 696
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
ticdc: update ticdc-debezium.md #19544
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Note: Do not use hard Tabs in our documentation. Hard Tabs make the CI check fail. I've replaced each hard Tab with four spaces via the 852aa42 commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Co-authored-by: xixirangrang <[email protected]>
ticdc/ticdc-debezium.md
Outdated
|
||
- Debezium converts `charsetName` to `"utf8mb4"` when the column collation is `"utf8_unicode_ci"` and the character set is null, but TiCDC does not. | ||
|
||
- Debezium escapes ENUM elements, but TiCDC does not. For example, Debezium encodes ENUM elements ('c', 'd', 'g,''h') to ('c','d','g,\'\'h'). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the example @wk989898. It does not display well.
Co-authored-by: nhsmw <[email protected]>
Co-authored-by: nhsmw <[email protected]>
Content is ready except the note #19544 (comment). |
| `payload.source.commit_ts` | Number | The `CommitTs` value of the event. | | ||
| `payload.source.db` | String | The name of the database where the event occurs. | | ||
| `payload.source.table` | String | The name of the table where the event occurs. | | ||
| `schema.fields` | JSON | The type information of each field in the payload, including the schema information of the row data before and after the change. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| `schema.fields` | JSON | The type information of each field in the payload, including the schema information of the row data before and after the change. | | |
| `schema.fields` | JSON | The type information of each field in the payload, including the schema information of the row data before and after the change. | | |
| `schema.fields[1].fields[n].tidb_type` | string | The tidb type of each column in the `payload.after`. it occurs when `enable-tidb-extension = true` | |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?