From 1f954231e8d3b47ae093663fd066e00c1ec4b132 Mon Sep 17 00:00:00 2001 From: josh-wong Date: Fri, 31 Jan 2025 03:05:08 +0000 Subject: [PATCH] AUTO: Sync ScalarDB docs in English to docs site repo --- versioned_docs/version-3.12/requirements.mdx | 2 +- ...ransactional-storage-operations-through-scalardb-cluster.mdx | 2 +- ...n-transactional-storage-operations-through-sql-interface.mdx | 2 +- versioned_docs/version-3.12/schema-loader-import.mdx | 2 +- versioned_docs/version-3.12/schema-loader.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/versioned_docs/version-3.12/requirements.mdx b/versioned_docs/version-3.12/requirements.mdx index bb3afece..cb6c0539 100644 --- a/versioned_docs/version-3.12/requirements.mdx +++ b/versioned_docs/version-3.12/requirements.mdx @@ -28,7 +28,7 @@ The following Java Development Kits (JDKs) are verified and supported. ### .NET -ScalarDB is provided as a gRPC server called ScalarDB Cluster, which also has a [.NET client SDK](https://scalardb.scalar-labs.com/docs/latest/scalardb-cluster-dotnet-client-sdk/overview/) that wraps the .NET client generated from the proto file. The SDK is a .NET Standard 2.0 library, so it should work with every implementation and its version that is supported by .NET Standard 2.0. However, the detailed supported implementations and their versions are to be decided. +ScalarDB is provided as a gRPC server called ScalarDB Cluster, which also has a [.NET client SDK](scalardb-cluster-dotnet-client-sdk/index.mdx) that wraps the .NET client generated from the proto file. The SDK is a .NET Standard 2.0 library, so it should work with every implementation and its version that is supported by .NET Standard 2.0. However, the detailed supported implementations and their versions are to be decided. ### Other languages diff --git a/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx b/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx index 2fce0d59..2aa66795 100644 --- a/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx +++ b/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx @@ -215,7 +215,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account -For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](configurations.mdx). +For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](../configurations.mdx). ## Set up ScalarDB Cluster in standalone mode diff --git a/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx b/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx index c6bc77f9..ff5ba9ec 100644 --- a/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx +++ b/versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx @@ -214,7 +214,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account -For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](configurations.mdx). +For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](../configurations.mdx). ## Set up ScalarDB Cluster in standalone mode diff --git a/versioned_docs/version-3.12/schema-loader-import.mdx b/versioned_docs/version-3.12/schema-loader-import.mdx index 23b16d15..3d0ef555 100644 --- a/versioned_docs/version-3.12/schema-loader-import.mdx +++ b/versioned_docs/version-3.12/schema-loader-import.mdx @@ -77,7 +77,7 @@ The following is a sample schema for importing tables. For the sample schema fil } ``` -The import table schema consists of a namespace name, a table name, and a `transaction` field. The `transaction` field indicates whether the table will be imported for transactions or not. If you set the `transaction` field to `true` or don't specify the `transaction` field, this tool creates a table with transaction metadata if needed. If you set the `transaction` field to `false`, this tool imports a table without adding transaction metadata (that is, for a table using the [Storage API](storage-abstraction.mdx)). +The import table schema consists of a namespace name, a table name, and a `transaction` field. The `transaction` field indicates whether the table will be imported for transactions or not. If you set the `transaction` field to `true` or don't specify the `transaction` field, this tool creates a table with transaction metadata if needed. If you set the `transaction` field to `false`, this tool imports a table without adding transaction metadata (that is, for a table using the [Storage API](run-non-transactional-storage-operations-through-primitive-crud-interface.mdx)). ## Data-type mapping from JDBC databases to ScalarDB diff --git a/versioned_docs/version-3.12/schema-loader.mdx b/versioned_docs/version-3.12/schema-loader.mdx index 7c18f71d..1db2a574 100644 --- a/versioned_docs/version-3.12/schema-loader.mdx +++ b/versioned_docs/version-3.12/schema-loader.mdx @@ -459,7 +459,7 @@ The schema has table definitions that include `columns`, `partition-key`, `clust - The `secondary-index` field defines which columns are indexed. - The `transaction` field indicates whether the table is for transactions or not. - If you set the `transaction` field to `true` or don't specify the `transaction` field, this tool creates a table with transaction metadata if needed. - - If you set the `transaction` field to `false`, this tool creates a table without any transaction metadata (that is, for a table with [Storage API](storage-abstraction.mdx)). + - If you set the `transaction` field to `false`, this tool creates a table without any transaction metadata (that is, for a table with [Storage API](run-non-transactional-storage-operations-through-primitive-crud-interface.mdx)). You can also specify database or storage-specific options in the table definition as follows: