TiDB v5.3 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. The following video introduces key now supported by TiDB so CREATE �→ TEMPORARY �→ TABLE and DROP �→ TEMPORARY �→ TABLE no longer require enabling tidb_enable_noop_functions �→ . 29 Variable name Change type Description tidb_enable in the Intel x86-64 architecture or on the hardware server platform in the ARM architecture. The require- ments and recommendations about server hardware configuration (ignoring the resources occupied by0 码力 | 2996 页 | 49.30 MB | 1 年前3
TiDB v5.2 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. 2.1.1 Key features • Horizontally in the Intel x86-64 architecture or on the hardware server platform in the ARM architecture. The require- ments and recommendations about server hardware configuration (ignoring the resources occupied by Memory Local Storage Network Instance Number (Minimum Requirement) TiDB 8 core+ 16 GB+ No special require- ments Gigabit network card 1 (can be deployed on the same machine with PD) 98 ComponentCPU Memory0 码力 | 2848 页 | 47.90 MB | 1 年前3
TiDB v5.1 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. 2.1.1 Key features • Horizontally in the Intel x86-64 architecture or on the hardware server platform in the ARM architecture. The require- ments and recommendations about server hardware configuration (ignoring the resources occupied by Memory Local Storage Network Instance Number (Minimum Requirement) TiDB 8 core+ 16 GB+ No special require- ments Gigabit network card 1 (can be deployed on the same machine with PD) 90 ComponentCPU Memory0 码力 | 2745 页 | 47.65 MB | 1 年前3
TiDB v5.4 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. The following video introduces key consistent history read. The strongly consistent read mode is suitable for application scenarios that require real-time data. However, in this mode, because of the data replication latency between leaders and the indexes in individual columns. Index Merge avoids unnecessary full table scans and does not require establishing a large number of composite indexes. In v5.4.0, Index Merge becomes GA. However, you0 码力 | 3650 页 | 52.72 MB | 1 年前3
TiDB v7.6 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. The following video introduces key Real-time HTAP scenarios TiDB is ideal for scenarios with massive data and high concurrency that require real- time processing. TiDB introduces the TiFlash columnar storage engine in v4.0, which combines are not sure what an optimistic transaction is, do NOT use it yet. Because optimistic transactions require that the application can correctly handle all errors re- turned by the COMMIT statement. If you are0 码力 | 6123 页 | 107.24 MB | 1 年前3
TiDB v8.5 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. TiDB Self-Managed is a product option Real-time HTAP scenarios TiDB is ideal for scenarios with massive data and high concurrency that require real- time processing. TiDB introduces the TiFlash columnar storage engine in v4.0, which combines are not sure what an optimistic transaction is, do NOT use it yet. Because optimistic transactions require that the application can correctly handle all errors re- turned by the COMMIT statement. If you are0 码力 | 6730 页 | 111.36 MB | 10 月前3
TiDB v8.4 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. TiDB Self-Managed is a product option Real-time HTAP scenarios TiDB is ideal for scenarios with massive data and high concurrency that require real- time processing. TiDB introduces the TiFlash columnar storage engine in v4.0, which combines are not sure what an optimistic transaction is, do NOT use it yet. Because optimistic transactions require that the application can correctly handle all errors re- turned by the COMMIT statement. If you are0 码力 | 6705 页 | 110.86 MB | 10 月前3
TiDB v8.3 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. The following video introduces key Real-time HTAP scenarios TiDB is ideal for scenarios with massive data and high concurrency that require real- time processing. TiDB introduces the TiFlash columnar storage engine in v4.0, which combines default, TiDB only collects statistics for columns with indexes and columns that are observed to require statistics collection. This speeds up the collection of statistics and avoids unnecessary resource0 码力 | 6606 页 | 109.48 MB | 10 月前3
TiDB v6.1 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. The following video introduces key to recover TiKV one by one. Since TiDB v6.1.0, the recovery process is fully automated, does not require to stop TiKV, and does not affect other applications online. The recovery process can be triggered Variable name Change type Description require_secure_transport �→ Newly added This set- ting was pre- vi- ously a tidb �→ . �→ toml �→ op- tion (security �→ . �→ require �→ - �→ secure �→ - �→ transport �→0 码力 | 4487 页 | 84.44 MB | 1 年前3
TiDB v6.5 DocumentationOLAP (Online Analytical Processing), and HTAP services. TiDB is suitable for various use cases that require high availability and strong consistency with large-scale data. The following video introduces key default_password_lifetime �→ Newly added Sets the global policy for auto- matic pass- word expira- tion to require users to change pass- words period- ically. The default value 0 indi- cates that pass- words never are not sure what an optimistic transaction is, do NOT use it yet. Because optimistic transactions require that the application can correctly handle all errors re- turned by the COMMIT statement. If you are0 码力 | 5282 页 | 99.69 MB | 1 年前3
共 32 条
- 1
- 2
- 3
- 4













