"type": , "producer": { }, "consumer": { <consumer settings> }, "processor": { }, } Due { ... }, "consumer": { ... }, "processor": { ... } } The command itself doesn't do anything. It must be followed by any other query: @export { "type": "csv", "producer": { ... }, "consumer": { ... } affect how the data is extracted. See the full table of supported settings in . the main section consumer Settings that affect how the data is transformed before processing. See the full table of supported

"type": , "producer": { }, "consumer": { <consumer settings> }, "processor": { }, } Due { ... }, "consumer": { ... }, "processor": { ... } } The command itself doesn't do anything. It must be followed by any other query: @export { "type": "csv", "producer": { ... }, "consumer": { ... } affect how the data is extracted. See the full table of supported settings in . the main section consumer Settings that affect how the data is transformed before processing. See the full table of supported

"type": , "producer": { }, "consumer": { <consumer settings> }, "processor": { }, } Due { ... }, "consumer": { ... }, "processor": { ... } } The command itself doesn't do anything. It must be followed by any other query: @export { "type": "csv", "producer": { ... }, "consumer": { ... } affect how the data is extracted. See the full table of supported settings in . the main section consumer Settings that affect how the data is transformed before processing. See the full table of supported

"type": , "producer": { }, "consumer": { <consumer settings> }, "processor": { }, } Due written on a single line, without line delimiters: @export { "type": "csv", "producer": { ... }, "consumer": { ... }, "processor": { ... } } Here's the description of each attribute: Attribute Description affect how the data is extracted. See the full table of supported settings in . the main section consumer Settings that affect how the data is transformed before processing. See the full table of supported

"type": , "producer": { }, "consumer": { <consumer settings> }, "processor": { }, } Due written on a single line, without line delimiters: @export { "type": "csv", "producer": { ... }, "consumer": { ... }, "processor": { ... } } Here's the description of each attribute: Attribute Description affect how the data is extracted. See the full table of supported settings in . the main section consumer Settings that affect how the data is transformed before processing. See the full table of supported

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3005 13.10.10Binlog Consumer Client User Guide · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3008 13.10.11TiDB replicates data from TiDB to Kafka. 3. Write data to TiDB using go-tpc. 4. Observe data on Kafka console consumer and check that the data is replicated to a specified Kafka topic. 5. (Optional) Configure the Flink data to the Kafka topic. Run kafka- �→ console-consumer.sh. You can see that data is successfully written to the Kafka topic. ./bin/kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 -- �→ from-beginning

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3039 13.10.10Binlog Consumer Client User Guide · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3042 13.10.11TiDB replicates data from TiDB to Kafka. 3. Write data to TiDB using go-tpc. 4. Observe data on Kafka console consumer and check that the data is replicated to a specified Kafka topic. 5. (Optional) Configure the Flink data to the Kafka topic. Run kafka- �→ console-consumer.sh. You can see that data is successfully written to the Kafka topic. ./bin/kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 -- �→ from-beginning

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3070 13.10.10Binlog Consumer Client User Guide · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3073 13.10.11TiDB replicates data from TiDB to Kafka. 3. Write data to TiDB using go-tpc. 4. Observe data on Kafka console consumer and check that the data is replicated to a specified Kafka topic. 5. (Optional) Configure the Flink data to the Kafka topic. Run kafka- �→ console-consumer.sh. You can see that data is successfully written to the Kafka topic. ./bin/kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 -- �→ from-beginning

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3095 13.10.10Binlog Consumer Client User Guide · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3098 13.10.11TiDB replicates data from TiDB to Kafka. 3. Write data to TiDB using go-tpc. 4. Observe data on Kafka console consumer and check that the data is replicated to a specified Kafka topic. 5. (Optional) Configure the Flink data to the Kafka topic. Run kafka- �→ console-consumer.sh. You can see that data is successfully written to the Kafka topic. ./bin/kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 -- �→ from-beginning

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3102 13.10.10Binlog Consumer Client User Guide · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 3105 13.10.11TiDB replicates data from TiDB to Kafka. 3. Write data to TiDB using go-tpc. 4. Observe data on Kafka console consumer and check that the data is replicated to a specified Kafka topic. 5. (Optional) Configure the Flink data to the Kafka topic. Run kafka- �→ console-consumer.sh. You can see that data is successfully written to the Kafka topic. ./bin/kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 -- �→ from-beginning