Y Y Y Y TiDB Bin- log 7 Y Y Y Y Y Y Y Y Y Y Change data cap- ture (CDC) Y Y Y Y Y Y Y Y Y Y Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y Y E N N N N N N N 7Starting different processing engines based on the specific business. • Real-time stream processing When using TiDB in real-time stream processing scenarios, TiDB ensures that all the data flowed in constantly in the URL. Then, resultset is automatically closed but the result set to be read in the previous stream- ing query is lost. • To use Cursor Fetch, first set FetchSize as a positive integer and configure

with TiCDC. After pausing data replication and conducting pre-online read-write tests in your down- stream TiDB cluster, this feature allows the cluster to gracefully and quickly roll back to the paused TSO race in some scenarios #49677 @lcwangchao • Fix the issue that query results are incorrect due to STREAM_AGG() incorrectly handling CI #49902 @wshwsh12 • Fix the issue that encoding fails when converting the issue that enforced sorting might become ineffective when a query uses optimizer hints (such as STREAM_AGG()) that enforce sorting and its execution plan contains IndexMerge #49605 @AilinKid • Fix the

TiDB Data Migration (DM) • Fix the issue that a task-mode:all task cannot be started when the up- stream database enables the GTID mode but does not have any data #7037 @liumengya94 88 • Fix the issue toolkit (DM) Y Y Y Y Y Y Y Y TiDB Binlog Y Y Y Y Y Y Y Y Change data capture (CDC) Y Y Y Y Y Y Y Y Stream data to Amazon S3, Azure Blob Storage, and NFS through TiCDC E N N N N N N N TiCDC supports bidirectional different processing engines based on the specific business. • Real-time stream processing When using TiDB in real-time stream processing scenarios, TiDB ensures that all the data flowed in constantly

does not guarantee atomicity. 93 Data im- port and ex- port 7.1 6.5 6.1 5.4 5.3 5.2 5.1 5.0 4.0 Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y E N N N N N N N TiCDC sup- different processing engines based on the specific business. • Real-time stream processing When using TiDB in real-time stream processing scenarios, TiDB ensures that all the data flowed in constantly in the URL. Then, resultset is automatically closed but the result set to be read in the previous stream- ing query is lost. • To use Cursor Fetch, first set FetchSize as a positive integer and configure

rolling back the partition DDL tasks #51090 @jiyfhust • Fix the issue that the value of max_remote_stream is incorrect when executing EXPLAIN ANALYZE #52646 @JaySon-Huang • Fix the issue that querying the Y Y Y Y Y Y TiDB Bin- log 6 Y Y Y Y Y Y Y Y Y Change data cap- ture (CDC) Y Y Y Y Y Y Y Y Y Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y Y Y E N N N N N back the different processing engines based on the specific business. • Real-time stream processing When using TiDB in real-time stream processing scenarios, TiDB ensures that all the data flowed in constantly

TiDB Bin- log 6 Deprecated Y Y Y Y Y Y Y Y Y Y Change data cap- ture (CDC) Y Y Y Y Y Y Y Y Y Y Y Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y Y Y Y Y E N N N N N transactions different processing engines based on the specific business. • Real-time stream processing When using TiDB in real-time stream processing scenarios, TiDB ensures that all the data flowed in constantly in the URL. Then, resultset is automatically closed but the result set to be read in the previous stream- ing query is lost. • The second method: Use Cursor Fetch by first setting FetchSize as a positive

Y Y Y Y TiDB Bin- log 6 Y Y Y Y Y Y Y Y Y Y Change data cap- ture (CDC) Y Y Y Y Y Y Y Y Y Y Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y Y Y Y E N N N N N back different processing engines based on the specific business. • Real-time stream processing When using TiDB in real-time stream processing scenarios, TiDB ensures that all the data flowed in constantly in the URL. Then, resultset is automatically closed but the result set to be read in the previous stream- ing query is lost. • To use Cursor Fetch, first set FetchSize as a positive integer and configure

rolling back the partition DDL tasks #51090 @jiyfhust • Fix the issue that the value of max_remote_stream is incorrect when executing EXPLAIN ANALYZE #52646 @JaySon-Huang • Fix the issue that querying the Y Y Y Y Y Y TiDB Bin- log 6 Y Y Y Y Y Y Y Y Y Change data cap- ture (CDC) Y Y Y Y Y Y Y Y Y Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y Y Y E N N N N N back the different processing engines based on the specific business. • Real-time stream processing When using TiDB in real-time stream processing scenarios, TiDB ensures that all the data flowed in constantly

batch �→ - �→ size Newly added Controls the max- imum size of each SQL query executed on the down- stream TiDB server in the logical import mode. The default value is "96KiB". The unit can be KB, KiB, MB added Specifies the file path of the secret key, which is used to encrypt and decrypt up- stream and down- stream pass- words. The file must contain a 64- character hexadeci- mal AES-256 secret key. 74 for data recovery. 94 Data im- port and ex- port 8.0 7.6 7.5 7.1 6.5 6.1 5.4 5.3 5.2 5.1 5.0 4.0 Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y Y Y Y E N N N N N N N TiCDC

4 Filter DML Events Using SQL Expressions · · · · · · · · · · · · · · · · · · · · · · · · 901 7 Stream Data 903 7.1 TiCDC Overview · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1195 7.6.8 How can I find out whether a DDL statement fails to execute in down- stream during TiCDC replication? How to resume the replication?· · · · 1196 7.6.9 The Kafka: client has TiCDC and PITR. 99 Data im- port and ex- port 8.4 8.3 8.2 8.1 7.5 7.1 6.5 6.1 5.4 5.3 5.2 5.1 Stream data to Ama- zon S3, GCS, Azure Blob Stor- age, and NFS through TiCDC Y Y Y Y Y Y E N N N N N TiCDC