Skip to content

Commit 1fc2323

Browse files
committed
AUTO: Sync ScalarDB docs in English to docs site repo
1 parent fc071b4 commit 1fc2323

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

versioned_docs/version-3.12/configurations.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,11 @@ If you are using ScalarDB Cluster, please refer to [ScalarDB Cluster Configurati
2222

2323
The following configurations are available for the Consensus Commit transaction manager:
2424

25-
| Name | Description | Default |
26-
|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
27-
| `scalar.db.transaction_manager` | Transaction manager of ScalarDB. Specify `consensus-commit` to use [Consensus Commit](./consensus-commit.mdx) or `single-crud-operation` to [run non-transactional storage operations](./run-non-transactional-storage-operations-through-library.mdx). Note that the configurations under the `scalar.db.consensus_commit` prefix are ignored if you use `single-crud-operation`. | `consensus-commit` |
28-
| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` |
29-
| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` |
25+
| Name | Description | Default |
26+
|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------------------|
27+
| `scalar.db.transaction_manager` | Transaction manager of ScalarDB. Specify `consensus-commit` to use [Consensus Commit](./consensus-commit.mdx). | `consensus-commit` |
28+
| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` |
29+
| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` |
3030

3131
## Performance-related configurations
3232

versioned_docs/version-3.12/scalardb-cluster/scalardb-cluster-configurations.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ The following general configurations are available for ScalarDB Cluster.
2121

2222
#### Transaction management configurations
2323

24-
| Name | Description | Default |
25-
|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
26-
| `scalar.db.transaction_manager` | Transaction manager of ScalarDB. Specify `consensus-commit` to use [Consensus Commit](../consensus-commit.mdx) or `single-crud-operation` to [run non-transactional storage operations](./run-non-transactional-storage-operations-through-scalardb-cluster.mdx). Note that the configurations under the `scalar.db.consensus_commit` prefix are ignored if you use `single-crud-operation`. | `consensus-commit` |
27-
| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` |
28-
| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` |
24+
| Name | Description | Default |
25+
|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------------------|
26+
| `scalar.db.transaction_manager` | Transaction manager of ScalarDB. Specify `consensus-commit` to use [Consensus Commit](../consensus-commit.mdx). | `consensus-commit` |
27+
| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` |
28+
| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` |
2929

3030
#### Node configurations
3131

0 commit comments

Comments
 (0)