Hello all, we are glad to announce the release of TiDB v5.1 and the short-term planning for the next version of TiDB.
You’re encouraged to leave your suggestion/comments to our planning; furthermore, if you’re interested in participating in any of the projects, feel free to contact us and join the feature crew, let’s improve TiDB together!
Attention: Code freeze for v5.2 will be called at Aug. 6th, and after that release-5.2 branch will be cut and all feature pull requests cannot merge to the release branch.
The planned features of TiDB Server are organized in SIGs, you are welcome to join the SIG for more details of those features.
|Aggregation spill to disk||#25882||wshwsh12||At present, HashAgg cannot spill to disk, which means that large joins that use HashAgg use a huge amount of memory and can trigger OOM.|
|Refactor the execution framework||XuHuaiyu||In order to enhance the resource management mechanism of tidb-server, we would like to provide a better parallel query framework for the runtime execution.|
|Enhance SQL Plan Management (SPM)||#25970||eurekaka||We would like to enhance the SPM of TiDB by providing the ability to auto capturing/binding the plans.|
|Plan Recreator||#26325||rebelice||A one-button dump and load utility is designed to help the DBA/developers better analyzing/improving the execution plans.|
|Improvement of index selection||#26020||winoros||We hope that the index selection of TiDB can be improved from the enhanced Heuristic/Skyline rules, a refined index cost model and formula, and a better strategy for indexes under severe stats.|
|Enhancement of cardinality estimation||#26085||time-and-fate||We plan to improve the out-of-Range/DNF/Limit/TopN estimation and provide a better selectivity under the severe stat.|
|The database-level placement rule in SQL||#18030||morgo||The database-level placement rule in SQL would provide a convenient solution to manipulate the placement rule for all objects in a database through the ‘DDL’ syntax in TiDB, which we believe, would enhance the usability of TiDB in the cross-region deployment scenario.|
|Temporary Table||#24169||djshow832||For now the
|A framework to provide the full character set support, as well as the GB18030 encoding||#25152||zimulala||Since the very initial version, TiDB supports the charset encoding for UTF-8(and its subset) only(
|Make expression index generally available||#25150||wjhuang2016||The ‘expression index’ of TiDB has been released in TiDB v4.0 as an experimental feature, now we think it is stable enough to be generally available by bringing a wider scope of integration tests.|
|Improve the ORM compatibility for TiDB||#24194||bb7133||We would like to provide a better experience for the developers who build applications on TiDB, by testing the ORM frameworks against TiDB and provide a specific TiDB adaptor if necessary, you can check this doc for the TiDBDialect we’ve done for Hibernate ORM.|
|Remove TiDB-to-TiDB RPC from tikv client||#25808||crazycs520||Now TiDB can access TiDB by RPC to grab some runtime information. It is implemented by defining a store type TiDB in the tikv client and all RPCs are served as coprocessor calls. However, a better way would be for TiDB to start its own gRPC client to access other TiDBs.|