Skip to content

AUTO: Docs repo sync - ScalarDB #908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 31, 2025
Merged

AUTO: Docs repo sync - ScalarDB #908

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion versioned_docs/version-3.12/requirements.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion ...b-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account
</TabItem>
</Tabs>

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

Expand Down
2 changes: 1 addition & 1 deletion ...ardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ You can use the primary key or the secondary key in your Azure Cosmos DB account
</TabItem>
</Tabs>

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

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.12/schema-loader-import.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.12/schema-loader.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down