-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[WIP] add release notes v9.0.0 #20035
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: preview-release-notes
Are you sure you want to change the base?
Conversation
Co-authored-by: Frank945946 <108602632+Frank945946@users.noreply.github.com>
concurrently-init-stats tidb_enable_index_merge_join
add note by joey
/cc @Oreoxmt |
@hfxsd: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@songrijie: adding LGTM is restricted to approvers and reviewers in OWNERS files. In 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. |
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…hash, and redact-info-log
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
* `MAX` | ||
* `MIN` | ||
* `COUNT` | ||
* `SUM` | ||
* `AVG` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* `MAX` | |
* `MIN` | |
* `COUNT` | |
* `SUM` | |
* `AVG` | |
* `MAX()` | |
* `MIN()` | |
* `COUNT()` | |
* `SUM()` | |
* `AVG()` |
- 如果升级前未指定过 [`format_version`](/tiflash/tiflash-configuration.md#format_version),升级后 TiFlash 默认采用新的存储格式。 | ||
- 如果升级前指定过 [`format_version`](/tiflash/tiflash-configuration.md#format_version),升级后 `format_version` 的值保持不变, TiFlash 会继续使用 `format_version` 指定的存储格式。此时如需启用新的存储格式,请在 TiFlash 配置文件中将 `format_version` 设置为 `8`。配置生效后,新写入 TiFlash 的数据将采用新的存储格式,而现有数据的存储格式则不受影响。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 如果升级前未指定过 [`format_version`](/tiflash/tiflash-configuration.md#format_version),升级后 TiFlash 默认采用新的存储格式。 | |
- 如果升级前指定过 [`format_version`](/tiflash/tiflash-configuration.md#format_version),升级后 `format_version` 的值保持不变, TiFlash 会继续使用 `format_version` 指定的存储格式。此时如需启用新的存储格式,请在 TiFlash 配置文件中将 `format_version` 设置为 `8`。配置生效后,新写入 TiFlash 的数据将采用新的存储格式,而现有数据的存储格式则不受影响。 | |
- 如果升级前未指定过 [`format_version`](/tiflash/tiflash-configuration.md#format_version),升级后 TiFlash 默认采用新的存储格式。 | |
- 如果升级前指定过 [`format_version`](/tiflash/tiflash-configuration.md#format_version),升级后 `format_version` 的值保持不变,TiFlash 会继续使用 `format_version` 指定的存储格式。此时如需启用新的存储格式,请在 TiFlash 配置文件中将 `format_version` 设置为 `8`。配置生效后,新写入 TiFlash 的数据将采用新的存储格式,而现有数据的存储格式则不受影响。 |
|
||
* TiFlash 支持新的存储格式以提升字符串类型扫描效率 [#9673](https://github.com/pingcap/tiflash/issues/9673) @[JinheLin](https://github.com/JinheLin) **tw@qiancai**<!--2066--> | ||
|
||
在 v9.0.0 版本之前,TiFlash 存储字符串类型数据的格式在扫描时需要逐行读取,因此对于长度较小的字符串数据,扫描效率不高。在 v9.0.0 中,TiFlash 引入了新的存储格式,针对字符串格式数据的存储进行了优化,提升了长度小于 64 字节的字符串数据扫描效率,且不会影响其他数据的存储和扫描性能。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
在 v9.0.0 版本之前,TiFlash 存储字符串类型数据的格式在扫描时需要逐行读取,因此对于长度较小的字符串数据,扫描效率不高。在 v9.0.0 中,TiFlash 引入了新的存储格式,针对字符串格式数据的存储进行了优化,提升了长度小于 64 字节的字符串数据扫描效率,且不会影响其他数据的存储和扫描性能。 | |
在 v9.0.0 版本之前,TiFlash 存储字符串类型数据的格式在扫描时需要逐行读取,导致短字符串的扫描效率较低。在 v9.0.0 中,TiFlash 引入了新的存储格式,针对字符串格式数据的存储进行了优化,提升了长度小于 64 字节的字符串数据的扫描效率,且不会影响其他数据的存储和扫描性能。 |
|
||
* 支持对分区表的非唯一列创建全局索引 [#58650](https://github.com/pingcap/tidb/issues/58650) @[Defined2014](https://github.com/Defined2014) @[mjonss](https://github.com/mjonss) **tw@qiancai**<!--2057--> | ||
|
||
从 v8.3.0 开始,TiDB 支持用户在分区表的唯一列上创建全局索引以提高查询性能,但不支持在非唯一列上创建全局索引。从 v9.0 版本起,TiDB 取消了这一限制,允许用户在分区表的非唯一列上创建全局索引,提升了全局索引的易用性。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
从 v8.3.0 开始,TiDB 支持用户在分区表的唯一列上创建全局索引以提高查询性能,但不支持在非唯一列上创建全局索引。从 v9.0 版本起,TiDB 取消了这一限制,允许用户在分区表的非唯一列上创建全局索引,提升了全局索引的易用性。 | |
从 v8.3.0 开始,TiDB 支持用户在分区表的唯一列上创建全局索引以提高查询性能,但不支持在非唯一列上创建全局索引。从 v9.0.0 起,TiDB 取消了这一限制,允许用户在分区表的非唯一列上创建全局索引,提升了全局索引的易用性。 |
First-time contributors' checklist
What is changed, added or deleted? (Required)
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 (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?