Skip to content

Commit 8899016

Browse files
AUTO: Sync ScalarDB docs in English to docs site repo (#908)
Co-authored-by: josh-wong <[email protected]>
1 parent f1b4844 commit 8899016

File tree

5 files changed

+5
-5
lines changed

5 files changed

+5
-5
lines changed

versioned_docs/version-3.12/requirements.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The following Java Development Kits (JDKs) are verified and supported.
2828

2929
### .NET
3030

31-
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.
31+
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.
3232

3333
### Other languages
3434

versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account
215215
</TabItem>
216216
</Tabs>
217217

218-
For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](configurations.mdx).
218+
For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](../configurations.mdx).
219219

220220
## Set up ScalarDB Cluster in standalone mode
221221

versioned_docs/version-3.12/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -214,7 +214,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account
214214
</TabItem>
215215
</Tabs>
216216

217-
For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](configurations.mdx).
217+
For a comprehensive list of configurations for ScalarDB, see [ScalarDB Configurations](../configurations.mdx).
218218

219219
## Set up ScalarDB Cluster in standalone mode
220220

versioned_docs/version-3.12/schema-loader-import.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ The following is a sample schema for importing tables. For the sample schema fil
7777
}
7878
```
7979

80-
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)).
80+
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)).
8181

8282
## Data-type mapping from JDBC databases to ScalarDB
8383

versioned_docs/version-3.12/schema-loader.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -459,7 +459,7 @@ The schema has table definitions that include `columns`, `partition-key`, `clust
459459
- The `secondary-index` field defines which columns are indexed.
460460
- The `transaction` field indicates whether the table is for transactions or not.
461461
- 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.
462-
- 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)).
462+
- 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)).
463463

464464
You can also specify database or storage-specific options in the table definition as follows:
465465

0 commit comments

Comments
 (0)