*: remove transaction kv count limit

dev/faq/tidb.md

@@ -915,7 +915,6 @@ As distributed transactions need to conduct two-phase commit and the bottom laye
 
 - A transaction is limited to 5000 SQL statements (by default)
 - Each Key-Value entry is no more than 6MB
-- The total number of Key-Value entry is no more than 300,000 rows
 - The total size of Key-Value entry is no more than 100MB
 
 There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Google Cloud Spanner.

dev/reference/transactions/transaction-model.md

@@ -26,7 +26,6 @@ Due to the distributed, 2-phase commit requirement of TiDB, large transactions t
 
 * A transaction is limited to 5000 SQL statements (by default)
 * Each Key-Value entry is no more than 6MB
-* The total number of Key-Value entries is no more than 300,000
 * The total size of Key-Value entries is no more than 100MB
 
 ### Small transactions

dev/tidb-in-kubernetes/reference/configuration/tidb-cluster.md

@@ -115,9 +115,6 @@ TiDB Operator uses `Helm` to deploy and manage TiDB clusters. The configuration
 | `tidb.txnLocalLatchesCapacity` |  The capacity of the transaction memory lock. The number of slots corresponding to Hash is automatically adjusted upward to an exponential multiple of `2`. Each slot occupies 32 Bytes of memory. When the range of writing data is relatively wide (such as importing data), setting this parameter too small a value results in lower performance.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`[txn-local-latches]`<br>`capacity = 10240000` | `10240000` |
 | `tidb.tokenLimit` | The restrictions on TiDB to execute concurrent sessions<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`token-limit = 1000` | `1000` |
 | `tidb.memQuotaQuery` | The memory quota for TiDB queries, which is 32GB by default.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`mem-quota-query = 34359738368` | `34359738368` |
-| `tidb.txnEntryCountLimit` | The limit on the number of entries in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`[performance]`<br>`txn-entry-count-limit = 300000` | `300000` |
-| `tidb.txnTotalSizeLimit` | The limit on byte size for each entry in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`[performance]`<br>`txn-total-size-limit = 104857600` | `104857600` |
-| `tidb.enableBatchDml` | Enables batch submission for DML.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`enable-batch-dml = false` | `false` |
 | `tidb.checkMb4ValueInUtf8` | Controls whether to check the `mb4` characters when the character set is `utf8`.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`check-mb4-value-in-utf8 = true` | `true` |
 | `tidb.treatOldVersionUtf8AsUtf8mb4` | This parameter is used for upgrading compatibility. When it is set to `true`, `utf8` character set in the old table/column is treated as `utf8mb4`.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`treat-old-version-utf8-as-utf8mb4 = true` | `true` |
 | `tidb.lease` | The lease time of TiDB Schema lease. It is highly risky to change this parameter. Therefore, it is not recommended to do so unless you know exactly what might be happening.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`lease = "45s"`  | `45s` |

v3.0/tidb-in-kubernetes/reference/configuration/tidb-cluster.md

@@ -115,9 +115,6 @@ TiDB Operator uses `Helm` to deploy and manage TiDB clusters. The configuration
 | `tidb.txnLocalLatchesCapacity` |  The capacity of the transaction memory lock. The number of slots corresponding to Hash is automatically adjusted upward to an exponential multiple of `2`. Each slot occupies 32 Bytes of memory. When the range of writing data is relatively wide (such as importing data), setting this parameter too small a value results in lower performance.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`[txn-local-latches]`<br>`capacity = 10240000` | `10240000` |
 | `tidb.tokenLimit` | The restrictions on TiDB to execute concurrent sessions<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`token-limit = 1000` | `1000` |
 | `tidb.memQuotaQuery` | The memory quota for TiDB queries, which is 32GB by default.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`mem-quota-query = 34359738368` | `34359738368` |
-| `tidb.txnEntryCountLimit` | The limit on the number of entries in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`[performance]`<br>`txn-entry-count-limit = 300000` | `300000` |
-| `tidb.txnTotalSizeLimit` | The limit on byte size for each entry in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`[performance]`<br>`txn-total-size-limit = 104857600` | `104857600` |
-| `tidb.enableBatchDml` | Enables batch submission for DML.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`enable-batch-dml = false` | `false` |
 | `tidb.checkMb4ValueInUtf8` | Controls whether to check the `mb4` characters when the character set is `utf8`.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`check-mb4-value-in-utf8 = true` | `true` |
 | `tidb.treatOldVersionUtf8AsUtf8mb4` | This parameter is used for upgrading compatibility. When it is set to `true`, `utf8` character set in the old table/column is treated as `utf8mb4`.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`treat-old-version-utf8-as-utf8mb4 = true` | `true` |
 | `tidb.lease` | The lease time of TiDB Schema lease. It is highly risky to change this parameter. Therefore, it is not recommended to do so unless you know exactly what might be happening.<br>If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:<br>`lease = "45s"`  | `45s` |