Last week, we published a post that introduces in detail how TiKV handles read and write operations. The post also explores how TiKV, as a distributed database, stores the data contained in a write request and how it retrieves the corresponding data with consistency guaranteed.
The full post is here:
tidb:
tikv:
docs:
docs-cn:
Last week, we landed 31 PRs in the TiDB repository, 8 PRs in the TiSpark repository, and 54 PRs in the TiKV and PD repositories.
TiDB:
TransformLimitToTableDual in the cascades plannerstream when reading the cluster memory tableinformation.tidb_hot_table for partitioned tablesPointGetPlan on the hash partitioned tableKindMysqlDuration and KindMysqlTimeTiSpark:
TiKV and PD:
random_bytesget_valid_int_prefix in the SELECT statement contextSTRING to REAL using the CAST functionlog_2args RPN function is inconsistent with TiDByymmddhhmm time format00:00:00 string is parsed to 2000-00-00 00:00:00RealPlus overflow is inconsistent with TiDB