BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties only affects newly written tables. For existing tables, the version information is read from the footer. • Optional values: • 0: Can be read by all TiKV versions. The default checksum type is CRC32 and

BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties

BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties only affects newly written tables. For existing tables, the version information is read from the footer. • Optional values: • 0: Can be read by all TiKV versions. The default checksum type is CRC32 and

BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties only affects newly written tables. For existing tables, the version information is read from the footer. • Optional values: • 0: Can be read by all TiKV versions. The default checksum type is CRC32 and

BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties only affects newly written tables. For existing tables, the version information is read from the footer. • Optional values: • 0: Can be read by all TiKV versions. The default checksum type is CRC32 and

BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties

BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties

value 的文件，其格式如下图所示： 2326 图 330: BlobFile BlobFile 由 blob record 、meta block、meta index block 和 footer 组成。其中每个 blob record 用于存放一个 key-value 对； meta block 支持可扩展性，可以用来存放和 BlobFile 相关的一些属性；meta index block 单位：KB|MB|GB 14.5.2.18.34 format-version 从 v6.2.0 版本开始引入 • 设置 SST 文件的格式版本。该配置项只影响新写入的表，对于已经存在的表，版本信息会从 footer 中读 取。 • 可选值： – 0：适用于所有 TiKV 版本。默认 checksum 类型为 CRC32。该版本不支持修改 checksum 类型。 – 1：适用于所有 TiKV 版本。支持使用非默认的

BlobFile Format A blob file mainly consists of blob records, meta blocks, a meta index block, and a footer. Each block record stores a Key-Value pair. The meta blocks are used for scalability, and store properties only affects newly written tables. For existing tables, the version information is read from the footer. • Optional values: • 0: Can be read by all TiKV versions. The default checksum type is CRC32 and

value 的文件，其格式如下图所示： 2211 图 314: BlobFile BlobFile 由 blob record 、meta block、meta index block 和 footer 组成。其中每个 blob record 用于存放一个 key-value 对； meta block 支持可扩展性，可以用来存放和 BlobFile 相关的一些属性；meta index block 单位：KB|MB|GB 14.5.2.18.34 format-version 从 v6.2.0 版本开始引入 • 设置 SST 文件的格式版本。该配置项只影响新写入的表，对于已经存在的表，版本信息会从 footer 中读 取。 • 可选值： – 0：适用于所有 TiKV 版本。默认 checksum 类型为 CRC32。该版本不支持修改 checksum 类型。 – 1：适用于所有 TiKV 版本。支持使用非默认的