diff --git a/versioned_docs/version-3.12/configurations.mdx b/versioned_docs/version-3.12/configurations.mdx index eef88921..bae3f8e1 100644 --- a/versioned_docs/version-3.12/configurations.mdx +++ b/versioned_docs/version-3.12/configurations.mdx @@ -22,11 +22,11 @@ If you are using ScalarDB Cluster, please refer to [ScalarDB Cluster Configurati The following configurations are available for the Consensus Commit transaction manager: -| Name | Description | Default | -|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| -| `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` | -| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` | -| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` | +| Name | Description | Default | +|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------------------| +| `scalar.db.transaction_manager` | Transaction manager of ScalarDB. Specify `consensus-commit` to use [Consensus Commit](./consensus-commit.mdx). | `consensus-commit` | +| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` | +| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` | ## Performance-related configurations diff --git a/versioned_docs/version-3.12/scalardb-cluster/scalardb-cluster-configurations.mdx b/versioned_docs/version-3.12/scalardb-cluster/scalardb-cluster-configurations.mdx index aa30c49f..9e6f7686 100644 --- a/versioned_docs/version-3.12/scalardb-cluster/scalardb-cluster-configurations.mdx +++ b/versioned_docs/version-3.12/scalardb-cluster/scalardb-cluster-configurations.mdx @@ -21,11 +21,11 @@ The following general configurations are available for ScalarDB Cluster. #### Transaction management configurations -| Name | Description | Default | -|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| -| `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` | -| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` | -| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` | +| Name | Description | Default | +|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|--------------------| +| `scalar.db.transaction_manager` | Transaction manager of ScalarDB. Specify `consensus-commit` to use [Consensus Commit](../consensus-commit.mdx). | `consensus-commit` | +| `scalar.db.consensus_commit.isolation_level` | Isolation level used for Consensus Commit. Either `SNAPSHOT`, `SERIALIZABLE`, or `READ_COMMITTED` can be specified. | `SNAPSHOT` | +| `scalar.db.consensus_commit.coordinator.namespace` | Namespace name of Coordinator tables used for Consensus Commit. | `coordinator` | #### Node configurations