-
Notifications
You must be signed in to change notification settings - Fork 680
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
releases: add TiDB 6.1.1 release notes #10139
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
releases/release-6.1.1.md
Outdated
+ TiDB | ||
|
||
<!-- <execution> --> | ||
- executor: fix index_lookup_hash_join hang when used with limit [#35638](https://github.com/pingcap/tidb/issues/35638) |
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.
Fix the issue that IndexLookupHashJoin may hangs when used with limit #35638
Fix the issue that TiDB may panic during update stmt #32311
Fix the bug that show columns
may send cop request #36496
Fix bug that show warnings
may return invalid memory address or nil pointer dereference
error #31569
Fix the case sensitive issues for show database like
statement #34766
Fix bug that static partition prune may return wrong result for agg query if the table is empty #35295
releases/release-6.1.1.md
Outdated
|
||
<!-- <planner> --> | ||
- planner: fix outer join reorder will push down its outer join condition [#37238](https://github.com/pingcap/tidb/issues/37238) | ||
- planner: fix cte-schema-clone will clone the old hashcode of its column if any [#35404](https://github.com/pingcap/tidb/issues/35404) |
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.
Fix outer join reorder will push down its outer join condition wrongly #37238
Fix that cte-schema hashcode is cloned wrongly when cte is referenced more than once #35404
Fix the wrong join reorder produced by some right outer join #36912
Fix the wrong nullable value infered for firstrow agg function with EqualAll #34584
Fix that plan cache cannot work when there's a binding with ignore_plan_cache hint #34596
Fix the missing exchange between hash-partition window and single-partition window #35990
Fix that some predicates are wrongly removed after partition pruning #33966
Fix the wrong default value set for partial aggregation when aggregation is pushed-down #35295
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.
@chrysan I think we don't need the 'component name' in the release note(they're useful for developers only), for example:
planner: fix the wrong join reorder produced by some right ouer join #36912
Could be simplified as:
Fix the wrong join reorder produced by some right ouer join #36912
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.
thx, updated.
releases/release-6.1.1.md
Outdated
+ PD | ||
|
||
- Fix the issue that the online process is not accurate when having invalid label settings. [#5234](https://github.com/tikv/pd/issues/5234) | ||
- grpc: fix the wrong error handler [#5373](https://github.com/tikv/pd/issues/5373) |
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.
releases/release-6.1.1.md
Outdated
(dup: release-5.3.2.md > Bug Fixes> TiKV)- Fix the issue of frequent PD client reconnection that occurs when the PD client meets an error [#12345](https://github.com/tikv/tikv/issues/12345) | ||
- Fix encryption keys not cleaned up when Raft Engine is enabled [#13123](https://github.com/tikv/tikv/issues/13123) | ||
(dup: release-6.2.0.md > Bug fixes> TiKV)- Fix the issue that the Commit Log Duration of a new Region is too high, which causes QPS to drop [#13077](https://github.com/tikv/tikv/issues/13077) | ||
(dup: release-6.2.0.md > Improvements> TiKV)- Support dynamically modifying the number of sub-compaction operations performed concurrently in RocksDB (`rocksdb.max-sub-compactions`) [#13145](https://github.com/tikv/tikv/issues/13145) |
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.
(dup: release-6.2.0.md > Improvements> TiKV)- Support dynamically modifying the number of sub-compaction operations performed concurrently in RocksDB (`rocksdb.max-sub-compactions`) [#13145](https://github.com/tikv/tikv/issues/13145) |
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.
It's moved to improvement.
releases/release-6.1.1.md
Outdated
|
||
- Fix a bug that regions may be overlapped if raftstore is too busy [#13160](https://github.com/tikv/tikv/issues/13160) | ||
(dup: release-6.2.0.md > Bug fixes> TiKV)- Fix the issue that PD does not reconnect to TiKV after the Region heartbeat is interrupted [#12934](https://github.com/tikv/tikv/issues/12934) | ||
- remove call_option to avoid deadlock(RWR). [#13191](https://github.com/tikv/tikv/issues/13191) |
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.
- remove call_option to avoid deadlock(RWR). [#13191](https://github.com/tikv/tikv/issues/13191) |
releases/release-6.1.1.md
Outdated
(dup: release-6.2.0.md > Bug fixes> TiKV)- Fix the issue of inconsistent Region size configuration between TiKV and PD [#12518](https://github.com/tikv/tikv/issues/12518) | ||
(dup: release-6.2.0.md > Bug fixes> TiKV)- Fix the issue that encryption keys are not cleaned up when Raft Engine is enabled [#12890](https://github.com/tikv/tikv/issues/12890) | ||
(dup: release-6.2.0.md > Bug fixes> TiKV)- Fix the panic issue that might occur when a peer is being split and destroyed at the same time [#12825](https://github.com/tikv/tikv/issues/12825) | ||
- Fix potential deadlock in `RpcClient` when two read locks are interleaved by a write lock. [#12933](https://github.com/tikv/tikv/issues/12933) |
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.
- Fix potential deadlock in `RpcClient` when two read locks are interleaved by a write lock. [#12933](https://github.com/tikv/tikv/issues/12933) |
Co-authored-by: Yexiang Zhang <mornyx.z@gmail.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: f15de7f
|
In response to a cherrypick label: new pull request created: #10301. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #10302. |
* This is an automated cherry-pick of #10139 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io> * Update releases/release-timeline.md * Apply suggestions from code review * Update releases/release-timeline.md * Update releases/release-timeline.md * Update releases/release-timeline.md Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io> Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?