TiDB Weekly

News & blog posts

Not long after we celebrated our 300th contributor milestone in September 2019, a new record, 400th contributor, is just created in our TiDB repository! Last week, we published a post written by our CTO Edward Huang to celebrate 400 contributors in our TiDB repository.

The full post is here:

TiDB Celebrates 400 Contributors

As the TiDB community expands and the TiDB project evolves, we're inspired to see contributors joining us and demonstrating their passion and pursuit of the open-source spirit. To get more people involved and included, we launched the TiDB Challenge Program, a series community program to bring TiDB to a new level in terms of stability, performance, and usability. With some amazing improvements in performance in season 1 last year, we published a post last week to announce that season 2 is ready for you.

The full post is here:

TiDB Usability Challenge - Dare to Dream Bigger

Community

New contributors

tidb:

• dasinlsb
• psinghal20
• peterepsteen

pd:

• loxp
• Poytr1

docs-cn:

• hjk0205

tidb-operator:

• tirsen

parser:

• gauss1314

chaos-mesh:

• tfulcrand

Call for participation

• Issues to solve for TiDB
• Issues to solve for TiKV

Updates of the week

Progress

Last week, we landed 90 PRs in the TiDB repository and 46 PRs in the TiKV and PD repositories.

Critical PRs

TiDB:

• Enable the dynamic configuration by default
• Support SELECT FOR UPDATE for BatchPointGet
• Push the collation information down to TiKV and MockTiKV
• Do not generate the partial aggregation when the cop-task has root conditions
• Add the DDL and DML privilege check for system tables
• Support BatchCommands for the RPC server to fix the panic in the batch connection heartbeat
• Refactor the TSO future in the RC isolation
• Add the implementation for SetCollationExpr in the planner
• Fix the issue that the CREATE TABLE LIKE statement does not split Regions on TiKV
• Support caching the prepare plan for the query on hash partitioned tables
• Add a channel to limit multiple DDL jobs being written at the same time

TiKV and PD:

• Enable the dynamic configuration by default
• Make sure that check keys do not exist
• Support CollationAware in compare_in
• Move WriteBatch from engine to engine_traits and rocks
• Add a Raftstore option to keep the data integration when half of peers fail

On-going TiDB event

TiDB Usability Challenge Program