What are the parameters and optional values for gRPC requests in the TiKV CDC module?

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

Original topic: 请问TiKV CDC 模块gRpc请求的参数以及可选值是什么?

| username: 迷人的Ti

Hello everyone, I am currently studying the principles of TiCDC. I have a basic understanding of handling CDC events, but the blog does not provide a detailed description of the gRPC requests to the CDC module. For example, what parameters are needed for this gRPC request, the meaning of each parameter, the possible values for each parameter, etc. Is there a comprehensive gRPC request documentation for the CDC module? Or how are the TiCDC requests written? I want to understand the meaning of each request and whether there is room for adjustment.

| username: wangccsy | Original post link

Newbie here to bump up your post.

| username: ljluestc | Original post link

  1. ChangefeedID: Represents a data capture task in CDC, usually a unique identifier.
  2. StartTs: Represents the starting timestamp of the change events to be captured.
  3. SinkURI: Represents the connection information of the target storage or processing system, which can be Kafka, MySQL, TiDB, etc.
  4. Config: Contains some configuration parameters, such as whether to enable filtering, DDL synchronization, etc.
  5. CaptureDMLs: Indicates whether to capture data manipulation statements, such as INSERT, UPDATE, DELETE.
  6. CaptureDDLs: Indicates whether to capture data definition statements, such as CREATE TABLE, ALTER TABLE.
  7. IgnoreErrors: Indicates whether to ignore errors and continue processing events.
  8. CheckpointTs: Represents the checkpoint captured by CDC, used to record the capture progress.
  9. SortEngine: Indicates the choice of sorting engine, which can be local or memory.
  10. MaxResolvedTs: Represents the maximum resolved timestamp.
  11. CDCVersion: Represents the TiCDC version.
| username: dba远航 | Original post link

Take a look at the official manual, it’s more comprehensive.