cleaning up stale regions might accidentally delete valid data #17258 @hbisheng • Fix the issue that Ingestion picked level and Compaction Job Size(files) are displayed incorrectly in the TiKV dashboard in 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

TiCDC and PITR. 94 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 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

major virtualized environments like VMware, KVM and XEN. • Red Hat Enterprise Linux 8.0, CentOS 8 Stream, and Oracle Enterprise Linux 8.0 are not supported yet as the testing of these platforms is in progress de- fault ini- tial- iza- tion com- mitTS -1 as the lat- est times- tamp; Con- fig- ure the down- stream tar- get TiDB as 10.0.1.12:4000 �→ 123 4.3.4.1.1 Topology templates • The simple template for Aggregating the count of rows both in TiDB (StreamAgg_20) and in TiKV ( ￿─ �→ StreamAgg_9) uses the stream aggregation, which is very efficient in its memory usage. The biggest issue with the current execution

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

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

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 major virtualized environments like VMware, KVM and XEN. • Red Hat Enterprise Linux 8.0, CentOS 8 Stream, and Oracle Enterprise Linux 8.0 are not supported yet as the testing of these platforms is in progress de- fault ini- tial- iza- tion com- mitTS -1 as the lat- est times- tamp; Con- fig- ure the down- stream tar- get TiDB as 10.0.1.12:4000 �→ 143 4.3.4.1.1 Topology templates • The simple template for

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 major virtualized environments like VMware, KVM and XEN. • Red Hat Enterprise Linux 8.0, CentOS 8 Stream, and Oracle Enterprise Linux 8.0 are not supported yet as the testing of these platforms is in progress de- fault ini- tial- iza- tion com- mitTS -1 as the lat- est times- tamp; Con- fig- ure the down- stream tar- get TiDB as 10.0.1.12:4000 �→ 131 4.3.4.1.1 Topology templates • The simple template for

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

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