[WIP] add v8.5.7 release notes#21764
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. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@JaySon-Huang: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
|
||
| - 改进部分索引与 BR 的兼容性,使 BR 在日志恢复期间修复 ingest 索引时能够保留其 `WHERE` 谓词 [#62664](https://github.com/pingcap/tidb/issues/62664) @[Leavrth](https://github.com/Leavrth) <!-- component: sql-infra --> | ||
| - 提升包含 `OR` 和 `IN` 条件的 `ORDER BY ... LIMIT` 查询性能。优化器现在可以更有效地选择 `IndexMerge`,并支持在 `IndexMerge` 的 `IN` 条件路径上使用 merge sort,从而将 `Limit` 下推到部分路径,减少不必要的行读取和 I/O 开销 [#65712](https://github.com/pingcap/tidb/issues/65712) @[time-and-fate](https://github.com/time-and-fate) <!-- component: planner --> <!--2262--> <!--tw:qiancai--> | ||
| - 改进慢查询可观测性,在 slow query log 中记录客户端连接属性,并在 `information_schema.slow_query` 和 `information_schema.cluster_slow_query` 中暴露这些属性;`performance_schema_session_connect_attrs_size` 现用于控制属性截断,并将被截断的字节数记录在 `_truncated` 中 [#66616](https://github.com/pingcap/tidb/issues/66616) @[jiong-nba](https://github.com/jiong-nba) <!-- component: observability --> <!--2374--> <!--tw:lilin90--> |
There was a problem hiding this comment.
| - 改进慢查询可观测性,在 slow query log 中记录客户端连接属性,并在 `information_schema.slow_query` 和 `information_schema.cluster_slow_query` 中暴露这些属性;`performance_schema_session_connect_attrs_size` 现用于控制属性截断,并将被截断的字节数记录在 `_truncated` 中 [#66616](https://github.com/pingcap/tidb/issues/66616) @[jiong-nba](https://github.com/jiong-nba) <!-- component: observability --> <!--2374--> <!--tw:lilin90--> | |
| - 改进慢查询可观测性,在 slow query log 中记录客户端连接属性,并可在 `INFORMATION_SCHEMA.SLOW_QUERY` 和 `INFORMATION_SCHEMA.CLUSTER_SLOW_QUERY` 中查询这些属性;`PERFORMANCE_SCHEMA_SESSION_CONNECT_ATTRS_SIZE` 现用于控制属性截断,并将被截断的字节数记录在 `_truncated` 中 [#66616](https://github.com/pingcap/tidb/issues/66616) @[jiong-nba](https://github.com/jiong-nba) <!-- component: observability --> <!--2374--> <!--tw:lilin90--> |
| - 提升 runaway query watch 处理的性能和稳定性,包括更可靠的 TiDB 实例间 watch 同步,以及更高效的后台 flush 和 sync [#65746](https://github.com/pingcap/tidb/issues/65746) @[JmPotato](https://github.com/JmPotato) <!-- component: pd (Although it is listed under the PD component label, in fact it only involves changes on the TiDB side )--> <!--2385--> | ||
| - 新增全局系统变量 `tidb_enable_batch_query_region`,用于控制 TiDB 是否向 PD 批量查询 Region 信息,从而提升获取 Region 信息的效率;该变量默认关闭 [#58439](https://github.com/pingcap/tidb/issues/58439) [#8690](https://github.com/tikv/pd/issues/8690) @[JmPotato](https://github.com/JmPotato) <!-- component: pd (this is only a change on the TiDB side,) --> <!--2463--> | ||
| - 改进多索引表查询的优化器性能,通过在代价估算前裁剪无关索引,降低查询规划时间,并避免不必要的全范围越界估算 [#63856](https://github.com/pingcap/tidb/issues/63856) @[terry1purcell](https://github.com/terry1purcell) @[qw4990](https://github.com/qw4990) <!-- component: planner --> <!--2315--> | ||
| - 增强 Blackbox exporter dashboard 中的 **Ping Latency** 面板,通过使用 `max_over_time` 告警规则新增 `Max Ping Latency` 指标。该变更使 dashboard 展示与 TiDB 告警逻辑保持一致,帮助你更容易识别延迟峰值并验证告警触发情况 [#1071](https://github.com/pingcap/monitoring/issues/1071) @[yibin87](https://github.com/yibin87) <!--2424--> <!--tw:qiancai--> |
There was a problem hiding this comment.
| - 增强 Blackbox exporter dashboard 中的 **Ping Latency** 面板,通过使用 `max_over_time` 告警规则新增 `Max Ping Latency` 指标。该变更使 dashboard 展示与 TiDB 告警逻辑保持一致,帮助你更容易识别延迟峰值并验证告警触发情况 [#1071](https://github.com/pingcap/monitoring/issues/1071) @[yibin87](https://github.com/yibin87) <!--2424--> <!--tw:qiancai--> | |
| - 增强 Blackbox exporter dashboard 中的 **Ping Latency** 面板,通过使用 `max_over_time` 告警规则新增 `Max Ping Latency` 指标。该变更使 dashboard 展示与 TiDB 告警逻辑保持一致,有助于更容易地识别延迟峰值并验证告警触发情况 [#1071](https://github.com/pingcap/monitoring/issues/1071) @[yibin87](https://github.com/yibin87) <!--2424--> <!--tw:qiancai--> |
| - 新增 redo checkpoint 和 resolved timestamp 指标,以提升 TiCDC redo log 进度的可观测性 [#5264](https://github.com/pingcap/ticdc/issues/5264) @[wk989898](https://github.com/wk989898) <!-- component: cdc --> | ||
| - 通过避免持久化未变化的运行时状态,缓解大量 TiCDC changefeed 进入 warning 状态时的 etcd 压力 [#5268](https://github.com/pingcap/ticdc/issues/5268) @[wk989898](https://github.com/wk989898) <!-- component: cdc --> | ||
| - 增强 TiCDC 监控,在 Changefeed Error Details Grafana 面板中展示错误发生时间,帮助运维人员更高效地诊断 changefeed 故障 [#5085](https://github.com/pingcap/ticdc/issues/5085) @[wlwilliamx](https://github.com/wlwilliamx) <!-- component: cdc --> | ||
| - 支持 TiCDC 中的表路由,通过在事件模型和 redo log 中保留下游 schema 和表名实现 [#4702](https://github.com/pingcap/ticdc/issues/4702) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> |
There was a problem hiding this comment.
| - 支持 TiCDC 中的表路由,通过在事件模型和 redo log 中保留下游 schema 和表名实现 [#4702](https://github.com/pingcap/ticdc/issues/4702) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> |
|
|
||
| 更多信息,请参考[用户文档](https://docs.pingcap.com/zh/tidb/v8.5/dm-compatibility-catalog#外键级联操作)。 | ||
|
|
||
| * TiCDC 支持表路由 [#4655](https://github.com/pingcap/ticdc/issues/4655) [#4941](https://github.com/pingcap/ticdc/issues/4941) @[3AceShowHand](https://github.com/3AceShowHand) <!--2471--><!--tw:qiancai--> |
There was a problem hiding this comment.
| * TiCDC 支持表路由 [#4655](https://github.com/pingcap/ticdc/issues/4655) [#4941](https://github.com/pingcap/ticdc/issues/4941) @[3AceShowHand](https://github.com/3AceShowHand) <!--2471--><!--tw:qiancai--> | |
| * TiCDC 支持表路由 [#4655](https://github.com/pingcap/ticdc/issues/4655) [#4941](https://github.com/pingcap/ticdc/issues/4941) [#4702](https://github.com/pingcap/ticdc/issues/4702) @[3AceShowHand](https://github.com/3AceShowHand) <!--2471--><!--tw:qiancai--> |
| - 优化 TiCDC MySQL sink 的冲突检测,以提升复制性能 [#4582](https://github.com/pingcap/ticdc/issues/4582) @[wk989898](https://github.com/wk989898) <!-- component: cdc --> | ||
| - 提升 TiCDC resolve lock 的可观测性,并避免对同一 Region 重复执行 resolve 尝试,以减少不必要的锁解析工作,并通过新增指标和 dashboard 让问题排查更容易 [#5016](https://github.com/pingcap/ticdc/issues/5016) @[lidezhu](https://github.com/lidezhu) <!-- component: cdc --> | ||
| - 在 TiCDC Grafana dashboard 中新增 Changefeed Operation History 面板,帮助排查最近由用户触发的 changefeed 操作,例如 create、update、pause、resume 和 delete [#5087](https://github.com/pingcap/ticdc/issues/5087) @[wlwilliamx](https://github.com/wlwilliamx) <!-- component: cdc --> | ||
| - 支持 TiCDC 解析和复制使用部分索引的 DDL 语句,包括带有 `WHERE` 子句的 `CREATE TABLE`、`CREATE INDEX` 和 `ALTER TABLE ... ADD INDEX` [#12503](https://github.com/pingcap/tiflow/issues/12503) @[YangKeao](https://github.com/YangKeao) <!-- component: cdc --> |
There was a problem hiding this comment.
| - 支持 TiCDC 解析和复制使用部分索引的 DDL 语句,包括带有 `WHERE` 子句的 `CREATE TABLE`、`CREATE INDEX` 和 `ALTER TABLE ... ADD INDEX` [#12503](https://github.com/pingcap/tiflow/issues/12503) @[YangKeao](https://github.com/YangKeao) <!-- component: cdc --> | |
| - 支持解析和同步使用部分索引的 DDL 语句,包括带有 `WHERE` 子句的 `CREATE TABLE`、`CREATE INDEX` 和 `ALTER TABLE ... ADD INDEX` [#12503](https://github.com/pingcap/tiflow/issues/12503) @[YangKeao](https://github.com/YangKeao) <!-- component: cdc --> |
| - 提升 TiCDC resolve lock 的可观测性,并避免对同一 Region 重复执行 resolve 尝试,以减少不必要的锁解析工作,并通过新增指标和 dashboard 让问题排查更容易 [#5016](https://github.com/pingcap/ticdc/issues/5016) @[lidezhu](https://github.com/lidezhu) <!-- component: cdc --> | ||
| - 在 TiCDC Grafana dashboard 中新增 Changefeed Operation History 面板,帮助排查最近由用户触发的 changefeed 操作,例如 create、update、pause、resume 和 delete [#5087](https://github.com/pingcap/ticdc/issues/5087) @[wlwilliamx](https://github.com/wlwilliamx) <!-- component: cdc --> | ||
| - 支持 TiCDC 解析和复制使用部分索引的 DDL 语句,包括带有 `WHERE` 子句的 `CREATE TABLE`、`CREATE INDEX` 和 `ALTER TABLE ... ADD INDEX` [#12503](https://github.com/pingcap/tiflow/issues/12503) @[YangKeao](https://github.com/YangKeao) <!-- component: cdc --> | ||
| - 在 TiCDC 中新增核心表路由支持,用于处理路由后 DDL 事件元数据和 DDL 查询重写 [#4941](https://github.com/pingcap/ticdc/issues/4941) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> |
There was a problem hiding this comment.
| - 在 TiCDC 中新增核心表路由支持,用于处理路由后 DDL 事件元数据和 DDL 查询重写 [#4941](https://github.com/pingcap/ticdc/issues/4941) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> |
| - 修复当 `MultipleTableInfos` 非空时,TiCDC 可能无法正确解码或错误处理多表 DDL 事件的问题 [#4415](https://github.com/pingcap/ticdc/issues/4415) @[asddongmen](https://github.com/asddongmen) <!-- component: cdc --> | ||
| - 修复 TiCDC 在复制 `EXCHANGE PARTITION` DDL 语句时,会破坏包含转义反引号的分区名的问题 [#4450](https://github.com/pingcap/ticdc/issues/4450) @[lidezhu](https://github.com/lidezhu) <!-- component: cdc --> | ||
| - 修复在并发更新 subscription checkpoint 时,TiCDC 可能在 event store 中生成乱序 checkpoint 更新,导致复制进度跟踪不一致的问题 [#4992](https://github.com/pingcap/ticdc/issues/4992) @[lidezhu](https://github.com/lidezhu) <!-- component: cdc --> | ||
| - 修复在表路由后,如果视图使用未别名的表限定列且源表带 schema 限定,TiCDC 可能生成无效 `CREATE VIEW` 语句的问题 [#5043](https://github.com/pingcap/ticdc/issues/5043) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> |
There was a problem hiding this comment.
| - 修复在表路由后,如果视图使用未别名的表限定列且源表带 schema 限定,TiCDC 可能生成无效 `CREATE VIEW` 语句的问题 [#5043](https://github.com/pingcap/ticdc/issues/5043) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> |
There was a problem hiding this comment.
reason: This issue does not exist for v8.5.6 and v8.5.7 users
First-time contributors' checklist
What is changed, added or deleted? (Required)
Add release note files for v8.5.7
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?