diff --git a/versioned_docs/version-3.13/api-guide.mdx b/versioned_docs/version-3.13/api-guide.mdx index 2ac1af20..d34b0978 100644 --- a/versioned_docs/version-3.13/api-guide.mdx +++ b/versioned_docs/version-3.13/api-guide.mdx @@ -581,7 +581,7 @@ And if you need to check if a value of a column is null, you can use the `isNull boolean isNull = result.isNull(""); ``` -For more details, see the `Result` page in the [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.1/index.html) of the version of ScalarDB that you're using. +For more details, see the `Result` page in the [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.2/index.html) of the version of ScalarDB that you're using. ###### Execute `Get` by using a secondary index diff --git a/versioned_docs/version-3.13/run-non-transactional-storage-operations-through-library.mdx b/versioned_docs/version-3.13/run-non-transactional-storage-operations-through-library.mdx index 9a432e50..ce808c07 100644 --- a/versioned_docs/version-3.13/run-non-transactional-storage-operations-through-library.mdx +++ b/versioned_docs/version-3.13/run-non-transactional-storage-operations-through-library.mdx @@ -237,7 +237,7 @@ Select your build tool, and follow the instructions to add the build dependency ```gradle dependencies { - implementation 'com.scalar-labs:scalardb:3.13.1' + implementation 'com.scalar-labs:scalardb:3.13.2' } ``` @@ -248,7 +248,7 @@ Select your build tool, and follow the instructions to add the build dependency com.scalar-labs scalardb - 3.13.1 + 3.13.2 ``` @@ -269,4 +269,4 @@ The following limitations apply to non-transactional storage operations: ### Learn more -- [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.1/index.html) +- [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.2/index.html) diff --git a/versioned_docs/version-3.13/scalardb-benchmarks/README.mdx b/versioned_docs/version-3.13/scalardb-benchmarks/README.mdx index 58ac6bd9..010d3e9d 100644 --- a/versioned_docs/version-3.13/scalardb-benchmarks/README.mdx +++ b/versioned_docs/version-3.13/scalardb-benchmarks/README.mdx @@ -1,6 +1,8 @@ --- tags: - Community + - Enterprise Standard + - Enterprise Premium displayed_sidebar: docsEnglish --- @@ -65,9 +67,11 @@ To build the benchmarking tools, run the following command: ### Load the schema -Before loading the initial data, the tables must be defined by using the [ScalarDB Schema Loader](../schema-loader.mdx). To apply the schema, go to the [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases) page and download the ScalarDB Schema Loader that matches the version of ScalarDB that you are using to the `scalardb-benchmarks` root folder. +Before loading the initial data, the tables must be defined by using the [ScalarDB Schema Loader](../schema-loader.mdx). You can download the ScalarDB Schema Loader on the [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases) page. Select the Schema Loader based on how you access ScalarDB: +- **Using the ScalarDB Core library (Community edition)?:** Choose `scalardb-schema-loader-.jar` for the version of ScalarDB that you're using. Then, save the `.jar` file in the `scalardb-benchmarks` root directory. +- **Using ScalarDB Cluster (Enterprise edition)?:** Choose `scalardb-cluster-schema-loader--all.jar` for the version of ScalarDB Cluster that you're using. Then, save the `.jar` file in the `scalardb-benchmarks` root directory. -In addition, you need a properties file that contains database configurations for ScalarDB. For details about configuring the ScalarDB properties file, see [ScalarDB Configurations](../configurations.mdx). +In addition, you need a properties file for accessing ScalarDB via the Java CRUD interface. For details about configuring the ScalarDB properties file, see [ScalarDB Configurations](../configurations.mdx) or [ScalarDB Cluster Client Configurations](../scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx#client-configurations). After applying the schema and configuring the properties file, select a benchmark and follow the instructions to create the tables. @@ -78,6 +82,12 @@ After applying the schema and configuring the properties file, select a benchmar ```console java -jar scalardb-schema-loader-.jar --config -f tpcc-schema.json --coordinator ``` + + If you are using ScalarDB Cluster, run the following command instead: + + ```console + java -jar scalardb-cluster-schema-loader--all.jar --config -f tpcc-schema.json --coordinator + ``` To create tables for YCSB benchmarking ([`ycsb-schema.json`](https://github.com/scalar-labs/scalardb-benchmarks/blob/master/ycsb-schema.json)), run the following command, replacing the contents in the angle brackets as described: @@ -85,6 +95,12 @@ After applying the schema and configuring the properties file, select a benchmar ```console java -jar scalardb-schema-loader-.jar --config -f ycsb-schema.json --coordinator ``` + + If you are using ScalarDB Cluster, run the following command instead: + + ```console + java -jar scalardb-cluster-schema-loader--all.jar --config -f ycsb-schema.json --coordinator + ``` To create tables for multi-storage YCSB benchmarking ([`ycsb-multi-storage-schema.json`](https://github.com/scalar-labs/scalardb-benchmarks/blob/master/ycsb-multi-storage-schema.json)), run the following command, replacing the contents in the angle brackets as described: @@ -92,6 +108,12 @@ After applying the schema and configuring the properties file, select a benchmar ```console java -jar scalardb-schema-loader-.jar --config -f ycsb-multi-storage-schema.json --coordinator ``` + + If you are using ScalarDB Cluster, run the following command instead: + + ```console + java -jar scalardb-cluster-schema-loader--all.jar --config -f ycsb-multi-storage-schema.json --coordinator + ``` diff --git a/versioned_docs/version-3.13/scalardb-cluster/compatibility.mdx b/versioned_docs/version-3.13/scalardb-cluster/compatibility.mdx index 2a7f30ec..0b469206 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/compatibility.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/compatibility.mdx @@ -13,6 +13,7 @@ This document shows the compatibility of ScalarDB Cluster versions among client | ScalarDB Cluster version | ScalarDB Cluster Java Client SDK version | ScalarDB Cluster .NET Client SDK version | |:-------------------------|:-----------------------------------------|:-----------------------------------------| +| 3.15 | 3.9 - 3.15 | 3.12* - 3.15 | | 3.14 | 3.9 - 3.14 | 3.12* - 3.14 | | 3.13 | 3.9 - 3.13 | 3.12* - 3.13 | | 3.12 | 3.9 - 3.12 | 3.12* | diff --git a/versioned_docs/version-3.13/scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx b/versioned_docs/version-3.13/scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx index cf3ea0be..bbbe057c 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api.mdx @@ -18,7 +18,7 @@ To add a dependency on the ScalarDB Cluster Java Client SDK by using Gradle, use ```gradle dependencies { - implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.1' + implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.2' } ``` @@ -28,7 +28,7 @@ To add a dependency by using Maven, use the following: com.scalar-labs scalardb-cluster-java-client-sdk - 3.13.1 + 3.13.2 ``` @@ -121,11 +121,11 @@ scalar.db.contact_points=direct-kubernetes:ns/scalardb-cluster To load a schema via ScalarDB Cluster, you need to use the dedicated Schema Loader for ScalarDB Cluster (Schema Loader for Cluster). Using the Schema Loader for Cluster is basically the same as using the [ScalarDB Schema Loader](../schema-loader.mdx) except the name of the JAR file is different. -You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1). +You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2). After downloading the JAR file, you can run Schema Loader for Cluster with the following command: ```console -java -jar scalardb-cluster-schema-loader-3.13.1-all.jar --config -f --coordinator +java -jar scalardb-cluster-schema-loader-3.13.2-all.jar --config -f --coordinator ``` ## ScalarDB Cluster SQL @@ -165,8 +165,8 @@ To add the dependencies on the ScalarDB Cluster JDBC driver by using Gradle, use ```gradle dependencies { - implementation 'com.scalar-labs:scalardb-sql-jdbc:3.13.1' - implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.1' + implementation 'com.scalar-labs:scalardb-sql-jdbc:3.13.2' + implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.2' } ``` @@ -177,12 +177,12 @@ To add the dependencies by using Maven, use the following: com.scalar-labs scalardb-sql-jdbc - 3.13.1 + 3.13.2 com.scalar-labs scalardb-cluster-java-client-sdk - 3.13.1 + 3.13.2 ``` @@ -200,8 +200,8 @@ To add the dependencies by using Gradle, use the following: ```gradle dependencies { - implementation 'com.scalar-labs:scalardb-sql-spring-data:3.13.1' - implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.1' + implementation 'com.scalar-labs:scalardb-sql-spring-data:3.13.2' + implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.2' } ``` @@ -212,12 +212,12 @@ To add the dependencies by using Maven, use the following: com.scalar-labs scalardb-sql-spring-data - 3.13.1 + 3.13.2 com.scalar-labs scalardb-cluster-java-client-sdk - 3.13.1 + 3.13.2 ``` @@ -262,10 +262,10 @@ For details about how to configure Spring Data JDBC for ScalarDB, see [Configura Like other SQL databases, ScalarDB SQL also provides a CLI tool where you can issue SQL statements interactively in a command-line shell. -You can download the SQL CLI for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1). After downloading the JAR file, you can run the SQL CLI with the following command: +You can download the SQL CLI for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2). After downloading the JAR file, you can run the SQL CLI with the following command: ```console -java -jar scalardb-cluster-sql-cli-3.13.1-all.jar --config +java -jar scalardb-cluster-sql-cli-3.13.2-all.jar --config ``` #### Usage @@ -273,7 +273,7 @@ java -jar scalardb-cluster-sql-cli-3.13.1-all.jar --config You can see the CLI usage with the `-h` option as follows: ```console -java -jar scalardb-cluster-sql-cli-3.13.1-all.jar -h +java -jar scalardb-cluster-sql-cli-3.13.2-all.jar -h Usage: scalardb-sql-cli [-hs] -c=PROPERTIES_FILE [-e=COMMAND] [-f=FILE] [-l=LOG_FILE] [-o=] [-p=PASSWORD] [-u=USERNAME] @@ -304,6 +304,6 @@ For details about the ScalarDB Cluster gRPC API, refer to the following: JavaDocs are also available: -* [ScalarDB Cluster Java Client SDK](https://javadoc.io/doc/com.scalar-labs/scalardb-cluster-java-client-sdk/3.13.1/index.html) -* [ScalarDB Cluster Common](https://javadoc.io/doc/com.scalar-labs/scalardb-cluster-common/3.13.1/index.html) -* [ScalarDB Cluster RPC](https://javadoc.io/doc/com.scalar-labs/scalardb-cluster-rpc/3.13.1/index.html) +* [ScalarDB Cluster Java Client SDK](https://javadoc.io/doc/com.scalar-labs/scalardb-cluster-java-client-sdk/3.13.2/index.html) +* [ScalarDB Cluster Common](https://javadoc.io/doc/com.scalar-labs/scalardb-cluster-common/3.13.2/index.html) +* [ScalarDB Cluster RPC](https://javadoc.io/doc/com.scalar-labs/scalardb-cluster-rpc/3.13.2/index.html) diff --git a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-graphql.mdx b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-graphql.mdx index 9aef47ce..6f386521 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-graphql.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-graphql.mdx @@ -106,11 +106,11 @@ For details about the client modes, see [Developer Guide for ScalarDB Cluster wi To load a schema via ScalarDB Cluster, you need to use the dedicated Schema Loader for ScalarDB Cluster (Schema Loader for Cluster). Using the Schema Loader for Cluster is basically the same as using the [Schema Loader for ScalarDB](../schema-loader.mdx) except the name of the JAR file is different. -You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1). +You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2). After downloading the JAR file, you can run the Schema Loader for Cluster with the following command: ```console -java -jar scalardb-cluster-schema-loader-3.13.1-all.jar --config database.properties -f schema.json --coordinator +java -jar scalardb-cluster-schema-loader-3.13.2-all.jar --config database.properties -f schema.json --coordinator ``` ## Step 4. Run operations from GraphiQL @@ -187,7 +187,7 @@ You should get the following result in the right pane: ### Mappings between GraphQL API and ScalarDB Java API The automatically generated GraphQL schema defines queries, mutations, and object types for input/output to allow you to run CRUD operations for all the tables in the target namespaces. -These operations are designed to match the ScalarDB APIs defined in the [`DistributedTransaction`](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.1/com/scalar/db/api/DistributedTransaction.html) interface. +These operations are designed to match the ScalarDB APIs defined in the [`DistributedTransaction`](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.2/com/scalar/db/api/DistributedTransaction.html) interface. Assuming you have an `account` table in a namespace, the following queries and mutations will be generated: diff --git a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-jdbc.mdx b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-jdbc.mdx index b69420c4..875f4f5f 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-jdbc.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-jdbc.mdx @@ -86,10 +86,10 @@ For details about the client modes, see [Developer Guide for ScalarDB Cluster wi ## Step 3. Load a schema -To load a schema, you need to use [the SQL CLI](developer-guide-for-scalardb-cluster-with-java-api.mdx#sql-cli). You can download the SQL CLI from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1). After downloading the JAR file, you can use SQL CLI for Cluster by running the following command: +To load a schema, you need to use [the SQL CLI](developer-guide-for-scalardb-cluster-with-java-api.mdx#sql-cli). You can download the SQL CLI from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2). After downloading the JAR file, you can use SQL CLI for Cluster by running the following command: ```console -java -jar scalardb-cluster-sql-cli-3.13.1-all.jar --config scalardb-sql.properties --file schema.sql +java -jar scalardb-cluster-sql-cli-3.13.2-all.jar --config scalardb-sql.properties --file schema.sql ``` ## Step 4. Load the initial data diff --git a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-spring-data-jdbc.mdx b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-spring-data-jdbc.mdx index 87961721..46c88d29 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-spring-data-jdbc.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster-sql-spring-data-jdbc.mdx @@ -86,10 +86,10 @@ For details about the client modes, see [Developer Guide for ScalarDB Cluster wi ## Step 3. Load a schema -To load a schema, you need to use [the SQL CLI](developer-guide-for-scalardb-cluster-with-java-api.mdx#sql-cli). You can download the SQL CLI from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1). After downloading the JAR file, you can use SQL CLI for Cluster by running the following command: +To load a schema, you need to use [the SQL CLI](developer-guide-for-scalardb-cluster-with-java-api.mdx#sql-cli). You can download the SQL CLI from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2). After downloading the JAR file, you can use SQL CLI for Cluster by running the following command: ```console -java -jar scalardb-cluster-sql-cli-3.13.1-all.jar --config scalardb-sql.properties --file schema.sql +java -jar scalardb-cluster-sql-cli-3.13.2-all.jar --config scalardb-sql.properties --file schema.sql ``` ## Step 4. Modify `application.properties` diff --git a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster.mdx b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster.mdx index 90f1a5e5..57caef38 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-scalardb-cluster.mdx @@ -120,7 +120,7 @@ To use ScalarDB Cluster, open `build.gradle` in your preferred text editor. Then dependencies { ... - implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.1' + implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.2' } ``` @@ -166,12 +166,12 @@ For details about the client modes, see [Developer Guide for ScalarDB Cluster wi The database schema (the method in which the data will be organized) for the sample application has already been defined in [`schema.json`](https://github.com/scalar-labs/scalardb-samples/tree/main/scalardb-sample/schema.json). -To apply the schema, go to [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1) and download the ScalarDB Cluster Schema Loader to the `scalardb-samples/scalardb-sample` folder. +To apply the schema, go to [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2) and download the ScalarDB Cluster Schema Loader to the `scalardb-samples/scalardb-sample` folder. Then, run the following command: ```console -java -jar scalardb-cluster-schema-loader-3.13.1-all.jar --config database.properties -f schema.json --coordinator +java -jar scalardb-cluster-schema-loader-3.13.2-all.jar --config database.properties -f schema.json --coordinator ``` #### Schema details diff --git a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-go-for-scalardb-cluster.mdx b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-go-for-scalardb-cluster.mdx index d671fff9..837975b5 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-go-for-scalardb-cluster.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-go-for-scalardb-cluster.mdx @@ -73,10 +73,10 @@ For details about the client modes, see [Developer Guide for ScalarDB Cluster wi ## Step 3. Load a schema -To load a schema via ScalarDB Cluster, you need to use the dedicated Schema Loader for ScalarDB Cluster (Schema Loader for Cluster). Using the Schema Loader for Cluster is basically the same as using the [Schema Loader for ScalarDB](../schema-loader.mdx) except the name of the JAR file is different. You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1). After downloading the JAR file, you can run the Schema Loader for Cluster with the following command: +To load a schema via ScalarDB Cluster, you need to use the dedicated Schema Loader for ScalarDB Cluster (Schema Loader for Cluster). Using the Schema Loader for Cluster is basically the same as using the [Schema Loader for ScalarDB](../schema-loader.mdx) except the name of the JAR file is different. You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2). After downloading the JAR file, you can run the Schema Loader for Cluster with the following command: ```console -java -jar scalardb-cluster-schema-loader-3.13.1-all.jar --config database.properties -f schema.json --coordinator +java -jar scalardb-cluster-schema-loader-3.13.2-all.jar --config database.properties -f schema.json --coordinator ``` ## Step 4. Set up a Go environment diff --git a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-python-for-scalardb-cluster.mdx b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-python-for-scalardb-cluster.mdx index 99b31026..633b4b9a 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-python-for-scalardb-cluster.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/getting-started-with-using-python-for-scalardb-cluster.mdx @@ -73,10 +73,10 @@ For details about the client modes, see [Developer Guide for ScalarDB Cluster wi ## Step 3. Load a schema -To load a schema via ScalarDB Cluster, you need to use the dedicated Schema Loader for ScalarDB Cluster (Schema Loader for Cluster). Using the Schema Loader for Cluster is basically the same as using the [Schema Loader for ScalarDB](../schema-loader.mdx) except the name of the JAR file is different. You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.1). After downloading the JAR file, you can run the Schema Loader for Cluster with the following command: +To load a schema via ScalarDB Cluster, you need to use the dedicated Schema Loader for ScalarDB Cluster (Schema Loader for Cluster). Using the Schema Loader for Cluster is basically the same as using the [Schema Loader for ScalarDB](../schema-loader.mdx) except the name of the JAR file is different. You can download the Schema Loader for Cluster from [ScalarDB Releases](https://github.com/scalar-labs/scalardb/releases/tag/v3.13.2). After downloading the JAR file, you can run the Schema Loader for Cluster with the following command: ```console -java -jar scalardb-cluster-schema-loader-3.13.1-all.jar --config database.properties -f schema.json --coordinator +java -jar scalardb-cluster-schema-loader-3.13.2-all.jar --config database.properties -f schema.json --coordinator ``` ## Step 4. Set up a Python environment diff --git a/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx b/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx index 6ff9cca4..7d6b37ed 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-scalardb-cluster.mdx @@ -271,7 +271,7 @@ Select your build tool, and follow the instructions to add the build dependency ```gradle dependencies { - implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.1' + implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.2' } ``` @@ -282,7 +282,7 @@ Select your build tool, and follow the instructions to add the build dependency com.scalar-labs scalardb-cluster-java-client-sdk - 3.13.1 + 3.13.2 ``` @@ -307,5 +307,5 @@ The following limitations apply to non-transactional storage operations: ### Learn more -- [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.1/index.html) +- [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.2/index.html) - [Developer Guide for ScalarDB Cluster with the Java API](developer-guide-for-scalardb-cluster-with-java-api.mdx) diff --git a/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx b/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx index 7d3e239f..d960d4ea 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/run-non-transactional-storage-operations-through-sql-interface.mdx @@ -276,8 +276,8 @@ Also, for a list of supported DDLs, see [ScalarDB SQL Grammar](../scalardb-sql/g ```gradle dependencies { - implementation 'com.scalar-labs:scalardb-sql-jdbc:3.13.1' - implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.1' + implementation 'com.scalar-labs:scalardb-sql-jdbc:3.13.2' + implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.2' } ``` @@ -289,12 +289,12 @@ Also, for a list of supported DDLs, see [ScalarDB SQL Grammar](../scalardb-sql/g com.scalar-labs scalardb-sql-jdbc - 3.13.1 + 3.13.2 com.scalar-labs scalardb-cluster-java-client-sdk - 3.13.1 + 3.13.2 ``` @@ -341,8 +341,8 @@ The following limitations apply to non-transactional storage operations: ```gradle dependencies { - implementation 'com.scalar-labs:scalardb-sql:3.13.1' - implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.1' + implementation 'com.scalar-labs:scalardb-sql:3.13.2' + implementation 'com.scalar-labs:scalardb-cluster-java-client-sdk:3.13.2' } ``` @@ -354,12 +354,12 @@ The following limitations apply to non-transactional storage operations: com.scalar-labs scalardb-sql - 3.13.1 + 3.13.2 com.scalar-labs scalardb-cluster-java-client-sdk - 3.13.1 + 3.13.2 ``` @@ -387,7 +387,7 @@ The following limitations apply to non-transactional storage operations:

Learn more

- - [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb-sql/3.13.1/index.html) + - [Javadoc](https://javadoc.io/doc/com.scalar-labs/scalardb-sql/3.13.2/index.html) diff --git a/versioned_docs/version-3.13/scalardb-cluster/setup-scalardb-cluster-on-kubernetes-by-using-helm-chart.mdx b/versioned_docs/version-3.13/scalardb-cluster/setup-scalardb-cluster-on-kubernetes-by-using-helm-chart.mdx index b2cbb7ca..32e88cc4 100644 --- a/versioned_docs/version-3.13/scalardb-cluster/setup-scalardb-cluster-on-kubernetes-by-using-helm-chart.mdx +++ b/versioned_docs/version-3.13/scalardb-cluster/setup-scalardb-cluster-on-kubernetes-by-using-helm-chart.mdx @@ -170,7 +170,7 @@ You can deploy PostgreSQL on the Kubernetes cluster as follows. 5. Set the chart version of ScalarDB Cluster. ```console - SCALAR_DB_CLUSTER_VERSION=3.13.1 + SCALAR_DB_CLUSTER_VERSION=3.13.2 SCALAR_DB_CLUSTER_CHART_VERSION=$(helm search repo scalar-labs/scalardb-cluster -l | grep -F "${SCALAR_DB_CLUSTER_VERSION}" | awk '{print $2}' | sort --version-sort -r | head -n 1) ``` diff --git a/versioned_docs/version-3.13/scalardb-graphql/getting-started-with-scalardb-graphql.mdx b/versioned_docs/version-3.13/scalardb-graphql/getting-started-with-scalardb-graphql.mdx deleted file mode 100644 index 1259d4e6..00000000 --- a/versioned_docs/version-3.13/scalardb-graphql/getting-started-with-scalardb-graphql.mdx +++ /dev/null @@ -1,235 +0,0 @@ -# Getting Started with ScalarDB GraphQL - -ScalarDB GraphQL is an interface layer that allows client applications to communicate with a [ScalarDB](https://github.com/scalar-labs/scalardb) database with GraphQL. - -In this Getting Started guide, you will run a GraphQL server on your local machine. - -## Prerequisites - -We assume you have already installed Docker and have access to a ScalarDB-supported database such as Cassandra. Please configure them first by following [Getting Started with ScalarDB](../getting-started-with-scalardb.mdx) if you have not set them up yet. - -You need a Personal Access Token (PAT) to access the Docker image of ScalarDB GraphQL in GitHub Container registry since the image is private. Ask a person in charge to get your account ready. Please read [the official document](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry) for more detail. - -## Set up a database schema - -We use the following simple example schema. - -`emoney.json` - -```json -{ - "emoney.account": { - "transaction": true, - "partition-key": [ - "id" - ], - "clustering-key": [], - "columns": { - "id": "TEXT", - "balance": "INT" - } - } -} -``` - -To apply the schema to your database, download the Schema Loader that matches the version you use from [scalardb releases](https://github.com/scalar-labs/scalardb/releases), and run the following command to load the schema. - -```console -java -jar scalardb-schema-loader-.jar --config /path/to/database.properties -f emoney.json --coordinator -``` - -## Docker login - -`docker login` is required to start the ScalarDB GraphQL Docker image as described in the Prerequisites section. - -```console -# read:packages scope needs to be selected in a personal access token to login -export CR_PAT=YOUR_PERSONAL_ACCESS_TOKEN -echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin -``` - -## Configure the GraphQL Server - -Add the following properties to your `database.properties` file. You can change the values as needed. Especially, make sure to set `namespaces` property. The tables in the specified namespaces (it can be a comma-separated list) will be exposed by the GraphQL server. - -```properties -scalar.db.graphql.port=8080 -scalar.db.graphql.path=/graphql -scalar.db.graphql.namespaces=emoney -scalar.db.graphql.graphiql=true -``` - -## Start up the GraphQL Server - -The following command starts up the ScalarDB GraphQL server. The first time you run the command, it will download the Docker image from GitHub Container Registry. - -```console -docker run -v /path/to/database.properties:/scalardb-graphql/database.properties.tmpl -p 8080:8080 ghcr.io/scalar-labs/scalardb-graphql: -``` - -At this point, the server reads the tables in the specified namespaces and generates a GraphQL schema to perform CRUD operations on the them. - -## Run operations from GraphiQL - -If the server is configured with a property `scalar.db.graphql.graphiql=true` (true by default), GraphiQL IDE will be available. When the above example properties are used, the endpoint URL of GraphiQL IDE is `http://localhost:8080/graphql`. Opening that URL with your web browser will take you to the GraphiQL screen. - -Let's insert the first record. In the left pane, paste the following mutation, then push the triangle-shaped `Execute Query` button at the top of the window. - -```graphql -mutation PutUser1 { - account_put(put: {key: {id: "user1"}, values: {balance: 1000}}) -} -``` - -ScalarDB GraphQL always runs queries with transactions. The above query starts a new transaction, executes a ScalarDB Put command, and commits the transaction at the end of the execution. - -The following response from the GraphQL server will appear in the right pane. - -```json -{ - "data": { - "account_put": true - } -} -``` - -The `"data"` field contains the result of the execution. This response shows the `account_put` field of the mutation was successful. The result type of mutations is `Boolean!`, which indicates whether the operation succeeded or not. - -Next, let's get the record you just inserted. Paste the following query next to the previous mutation in the left pane, and click the `Execute Query` button. Since you don't delete the `mutation PutUser1` above, a pull-down will appear below the button, and you can choose which operation should be executed. Choose `GetUser1`. - -```graphql -query GetUser1 { - account_get(get: {key: {id: "user1"}}) { - account { - id - balance - } - } -} -``` - -You should get the following result in the right pane. - -```json -{ - "data": { - "account_get": { - "account": { - "id": "user1", - "balance": 1000 - } - } - } -} -``` - -## Mappings between GraphQL API and ScalarDB Java API - -The automatically generated GraphQL schema defines queries, mutations, and object types for input/output to allow you to run CRUD operations for all the tables in the target namespaces. These operations are designed to match the ScalarDB APIs defined in the [`DistributedTransaction`](https://javadoc.io/doc/com.scalar-labs/scalardb/3.13.1/com/scalar/db/api/DistributedTransaction.html) interface. - -Assuming you have an `account` table in a namespace, the following queries and mutations will be generated. - -| ScalarDB API | GraphQL root type | GraphQL field | -|--------------------------------------------------------|-------------------|------------------------------------------------------------------------------------| -| `get(Get get)` | `Query` | `account_get(get: account_GetInput!): account_GetPayload` | -| `scan(Scan scan)` | `Query` | `account_scan(scan: account_ScanInput!): account_ScanPayload` | -| `put(Put put)` | `Mutation` | `account_put(put: account_PutInput!): Boolean!` | -| `put(java.util.List puts)` | `Mutation` | `account_bulkPut(put: [account_PutInput!]!): Boolean!` | -| `delete(Delete delete)` | `Mutation` | `account_delete(delete: account_DeleteInput!): Boolean!` | -| `delete(java.util.List deletes)` | `Mutation` | `account_bulkDelete(delete: [account_DeleteInput!]!): Boolean!` | -| `mutate(java.util.List mutations)` | `Mutation` | `account_mutate(put: [account_PutInput!]delete: [account_DeleteInput!]): Boolean!` | - -Note that the `scan` field is not generated for a table with no clustering key. This is the reason why `account_scan` field is not available in our `emoney` example in this document. - -You can see all generated GraphQL types in GraphiQL's Documentation Explorer (the `< Docs` link at the top-right corner). - -## Transaction across multiple requests - -This section describes how to run a transaction that spans multiple GraphQL requests. - -The generated schema provides the `@transaction` directive that allows you to identify transactions. This directive can be used with both queries and mutations. - -### Start a transaction before running an operation - -Adding a `@transaction` directive with no arguments to a query or a mutation directs the execution to start a new transaction. - -```graphql -query GetAccounts @transaction { - user1: account_get(get: {key: {id: "user1"}}) { - account { balance } - } - user2: account_get(get: {key: {id: "user2"}}) { - account { balance } - } -} -``` - -You will get a result with a transaction ID in the `extensions` field. The `id` value in the extensions is the transaction ID in which the operation in the request was run. In this case, this is the new ID of the transaction just started by the request. - -```json -{ - "data": { - "user1": { - "account": { - "balance": 1000 - } - }, - "user2": { - "account": { - "balance": 1000 - } - } - }, - "extensions": { - "transaction": { - "id": "c88da8a6-a13f-4857-82fe-45f1ab4150f9" - } - } -} -``` - -### Run an operation in a continued transaction - -To run the next queries or mutations in the transaction you started, specify the transaction ID as the `id` argument of the `@transaction`. The following example will update two accounts you got in the previous example in the same transaction. This represents a transfer of balance from user1's account to user2's account. - -```graphql -mutation Transfer @transaction(id: "c88da8a6-a13f-4857-82fe-45f1ab4150f9") { - user1: account_put(put: {key: {id: "user1"}, values: {balance: 750}}) - user2: account_put(put: {key: {id: "user2"}, values: {balance: 1250}}) -} -``` - -Note that a transaction started with GraphQL has a timeout of 1 minute and will be aborted automatically when it exceeds the timeout. - -### Commit a transaction - -To commit the continued transaction, specify both the `id` and the `commit: true` flag as arguments of the `@transaction` directive. - -```graphql -query GetAndCommit @transaction(id: "c88da8a6-a13f-4857-82fe-45f1ab4150f9", commit: true) { - user1: account_get(get: {key: {id: "user1"}}) { - account { balance } - } - user2: account_get(get: {key: {id: "user2"}}) { - account { balance } - } -} -``` - -Note: If you specify a `commit: true` flag without an `id` argument like `@transaction(commit: true)`, a new transaction is started and committed just for one operation. This is exactly the same as not specifying the `@transaction` directive, as seen in the above examples using GraphiQL. In other words, you can omit the directive itself when it is `@transaction(commit: true)`. - -### Abort/Rollback a transaction - -When you need to abort/rollback a transaction explicitly, you can use the `abort` or `rollback` mutation fields interchangeably (both have the same effect and usage). Note that you cannot mix it with any other operations, so you must specify it alone. - -```graphql -mutation AbortTx @transaction(id: "c88da8a6-a13f-4857-82fe-45f1ab4150f9") { - abort -} -``` -or -```graphql -mutation RollbackTx @transaction(id: "c88da8a6-a13f-4857-82fe-45f1ab4150f9") { - rollback -} -``` \ No newline at end of file diff --git a/versioned_docs/version-3.13/scalardb-graphql/index.mdx b/versioned_docs/version-3.13/scalardb-graphql/index.mdx deleted file mode 100644 index 289b7af0..00000000 --- a/versioned_docs/version-3.13/scalardb-graphql/index.mdx +++ /dev/null @@ -1,101 +0,0 @@ -# ScalarDB GraphQL Server - -ScalarDB GraphQL Server is an interface layer that allows client applications to communicate with [ScalarDB](https://github.com/scalar-labs/scalardb) with GraphQL. - -## Build & Install - -To build and install the ScalarDB GraphQL Server, use `./gradlew installDist`, which will build the source files and install an executable and required jars: - -```console -./gradlew installDist -``` - -## Run - -In addition to the configurations described in [Transaction manager configurations](../configurations.mdx#transaction-manager-configurations) and [Other configurations](../configurations.mdx#other-configurations), the GraphQL server reads the following: - -* `scalar.db.graphql.port` ... Port number for GraphQL server. The default is `8080`. -* `scalar.db.graphql.path` ... Path component of the URL of the GraphQL endpoint. The default is `/graphql`. -* `scalar.db.graphql.namespaces` ... Comma-separated list of namespaces of tables for which the GraphQL server generates a schema. Note that at least one namespace is required. -* `scalar.db.graphql.graphiql` ... Whether the GraphQL server serves [GraphiQL](https://github.com/graphql/graphiql) IDE. The default is `true`. -* `scalar.db.graphql.schema_checking_interval_millis` ... The interval at which GraphQL server will rebuild the GraphQL schema if any change is detected in the ScalarDB schema. - The default interval value is `30000` (30 seconds). Besides, this automatic schema rebuild can be disabled by setting the property value to `-1`. - Refer to the [following section](#creating-or-modifying-the-scalardb-schema-when-the-server-is-running) for more details. - -To start the ScalarDB GraphQL Server, run the following commands: - -```console -cd build/install/graphql -export JAVA_OPTS="" -bin/scalardb-graphql-server --config -``` - -### Creating or modifying the ScalarDB schema when the server is running - -Since the GraphQL schema is statically built at server startup, if the ScalarDB schema is modified (e.g., a table is added, altered or deleted) then the corresponding GraphQL schema -won't reflect the changes unless it is rebuilt. To address this, the GraphQL server provides the following two mechanisms: - -#### Periodic check - -The server periodically checks if changes in the ScalarDB schema occur and rebuilds the corresponding GraphQL schema -if necessary. By default, the checking occurs every 30 seconds, but the interval can be configured with the `scalar.db.graphql.schema_checking_interval_millis` property. -Besides, this periodic check can be disabled by setting the property value to `-1`. - -#### On-demand check - -We can also request the server to check changes in the ScalarDB schema and rebuild the corresponding GraphQL schema if necessary by performing a POST request to the `/update-graphql-schema` endpoint of the HTTP API. - -For example, if the HTTP API is running on `localhost` on port `8080` and the `scalar.db.graphql.path` property is set to `/graphql`. This endpoint can be called with : - -```console - curl -X POST http://localhost:8080/graphql/update-graphql-schema -``` - -## Docker - -### Build - -This builds the ScalarDB GraphQL Server Docker image: - -```console -./gradlew docker -``` - -### Run - -This runs the ScalarDB GraphQL Server (you need to specify your local configuration file path with `-v` flag): - -```console -docker run -d -p 8080:8080 \ - -v :/scalardb-graphql/database.properties.tmpl \ - ghcr.io/scalar-labs/scalardb-graphql: - -# For DEBUG logging -docker run -d -p 8080:8080 \ - -v :/scalardb-graphql/database.properties.tmpl \ - -e SCALAR_DB_GRAPHQL_LOG_LEVEL=DEBUG \ - ghcr.io/scalar-labs/scalardb-graphql: -``` - -You can also pass the database settings via environment variables: - -```console -docker run -d -p 8080:8080 \ - -e SCALAR_DB_CONTACT_POINTS=cassandra \ - -e SCALAR_DB_CONTACT_PORT=9042 \ - -e SCALAR_DB_USERNAME=cassandra \ - -e SCALAR_DB_PASSWORD=cassandra \ - -e SCALAR_DB_STORAGE=cassandra \ - -e SCALAR_DB_TRANSACTION_MANAGER=consensus-commit \ - -e SCALAR_DB_GRAPHQL_PATH=/graphql \ - -e SCALAR_DB_GRAPHQL_NAMESPACES=namespace1,namespace2 \ - -e SCALAR_DB_GRAPHQL_GRAPHIQL=true \ - -e SCALAR_DB_GRAPHQL_LOG_LEVEL=INFO \ - ghcr.io/scalar-labs/scalardb-graphql: -``` - -## Docs - -* [Getting Started with ScalarDB GraphQL](getting-started-with-scalardb-graphql.mdx) -* [How to run two-phase commit transaction](how-to-run-two-phase-commit-transaction.mdx) -* [Deployment Guide on AWS](aws-deployment-guide.mdx) diff --git a/versioned_docs/version-3.13/scalardb-sql/index.mdx b/versioned_docs/version-3.13/scalardb-sql/index.mdx deleted file mode 100644 index 26eac134..00000000 --- a/versioned_docs/version-3.13/scalardb-sql/index.mdx +++ /dev/null @@ -1,137 +0,0 @@ -# ScalarDB SQL - -ScalarDB SQL is an SQL layer for ScalarDB. -Specifically, it parses SQL and converts it to a set of ScalarDB (API) operations. - -## Install - -The libraries for ScalarDB SQL are available on the [Maven Central Repository](https://mvnrepository.com/artifact/com.scalar-labs/scalardb-sql) and as [packages on GitHub](https://github.com/orgs/scalar-labs/packages?repo_name=scalardb-sql). Since they are available under a commercial license, you need to get a license and permission to access them. For more details, please [contact us](https://scalar-labs.com/contact_us/). - -Before you add the dependency, you need to add the Maven repository using your build tool such as Gradle and Maven. - -To add the Maven repository using Gradle, add the following repository to your `build.gradle`: -```gradle -repositories { - maven { - url = uri("https://maven.pkg.github.com/scalar-labs/scalardb-sql") - credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") - } - } -} -``` - -In this case, you need the `gpr.user` property for your GitHub username and the `gpr.key` property for your personal access token. -So you need to have the properties in `~/.gradle/gradle.properties`, or specify the properties with the `-P` option when running the `./gradlew` command as follows: - -```console -./gradlew build -Pgpr.user= -Pgpr.key= -``` - -Or you can also use environment variables, `USERNAME` for your GitHub username and `TOKEN` for your personal access token. - -```console -export USERNAME= -export TOKEN= -``` - -To add the Maven repository using Maven, edit your `~/.m2/settings.xml` file as follows: -```xml - - - - github - - - - - github - - - central - https://repo1.maven.org/maven2 - - - github - https://maven.pkg.github.com/scalar-labs/scalardb-sql - - true - - - - - - - - - github - USERNAME - TOKEN - - - -``` - -In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your GitHub username, and *TOKEN* with your personal access token. - -Please see also the following documents for more details: -- [Working with the Gradle registry](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry) -- [Working with the Apache Maven registry](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry) - -And then, you can install the library in your application using your build tool such as Gradle and Maven. - -To add a dependency on ScalarDB SQL using Gradle, use the following: -```gradle -dependencies { - // For Direct mode - implementation 'com.scalar-labs:scalardb-sql-direct-mode:3.13.1' - - // For Server mode - implementation 'com.scalar-labs:scalardb-sql-server-mode:3.13.1' -} -``` - -To add a dependency using Maven: -```xml - - - - com.scalar-labs - scalardb-sql-direct-mode - 3.13.1 - - - - - com.scalar-labs - scalardb-sql-server-mode - 3.13.1 - - -``` - -## Docs - -- [Getting Started with ScalarDB SQL](getting-started-with-sql.mdx) -- [Getting Started with ScalarDB JDBC](getting-started-with-jdbc.mdx) -- [ScalarDB SQL API Guide](sql-api-guide.mdx) -- [ScalarDB JDBC Guide](jdbc-guide.mdx) -- [ScalarDB SQL Grammar](grammar.mdx) -- [ScalarDB SQL Command Line interface](command-line-interface.mdx) -- [ScalarDB SQL Server](sql-server.mdx) -- [ScalarDB SQL Configurations](configurations.mdx) -- [Guide of Spring Data JDBC for ScalarDB](spring-data-guide.mdx) -- Javadoc - - [scalardb-sql](https://scalar-labs.github.io/scalardb-sql/javadoc/core/index.html) - ScalarDB SQL: A SQL layer for ScalarDB - - [scalardb-direct-mode](https://scalar-labs.github.io/scalardb-sql/javadoc/direct-mode/index.html) - ScalarDB SQL Direct mode - - [scalardb-sql-rpc](https://scalar-labs.github.io/scalardb-sql/javadoc/rpc/index.html) - ScalarDB SQL RPC libraries - - [scalardb-sql-server](https://scalar-labs.github.io/scalardb-sql/javadoc/server/index.html) - ScalarDB SQL Server: A gRPC interface of ScalarDB SQL - - [scalardb-server-mode](https://scalar-labs.github.io/scalardb-sql/javadoc/server-mode/index.html) - ScalarDB SQL Server mode - - [scalardb-sql-jdbc](https://scalar-labs.github.io/scalardb-sql/javadoc/jdbc/index.html) - ScalarDB SQL JDBC: JDBC Driver for ScalarDB SQL - - [scalardb-sql-cli](https://scalar-labs.github.io/scalardb-sql/javadoc/cli/index.html) - ScalarDB SQL CLI: ScalarDB SQL Command Line Interface - - [scalardb-sql-integration-test](https://scalar-labs.github.io/scalardb-sql/javadoc/integration-test/index.html) - ScalarDB SQL Integration test: Integration tests for ScalarDB SQL - - [scalardb-sql-spring-data](https://scalar-labs.github.io/scalardb-sql/javadoc/spring-data/index.html) - Spring Data JDBC for ScalarDB: Spring Data JDBC integration for ScalarDB diff --git a/versioned_docs/version-3.13/scalardb-sql/jdbc-guide.mdx b/versioned_docs/version-3.13/scalardb-sql/jdbc-guide.mdx index 59c28c58..7dca1a5a 100644 --- a/versioned_docs/version-3.13/scalardb-sql/jdbc-guide.mdx +++ b/versioned_docs/version-3.13/scalardb-sql/jdbc-guide.mdx @@ -192,4 +192,4 @@ Please see also [ScalarDB SQL API Guide](sql-api-guide.mdx) for more details on - [Java JDBC API](https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/) - [ScalarDB SQL API Guide](sql-api-guide.mdx) -- [Javadoc for ScalarDB JDBC](https://javadoc.io/doc/com.scalar-labs/scalardb-sql-jdbc/3.13.1/index.html) +- [Javadoc for ScalarDB JDBC](https://javadoc.io/doc/com.scalar-labs/scalardb-sql-jdbc/3.13.2/index.html) diff --git a/versioned_docs/version-3.13/scalardb-sql/spring-data-guide.mdx b/versioned_docs/version-3.13/scalardb-sql/spring-data-guide.mdx index 926880ca..54475da2 100644 --- a/versioned_docs/version-3.13/scalardb-sql/spring-data-guide.mdx +++ b/versioned_docs/version-3.13/scalardb-sql/spring-data-guide.mdx @@ -814,4 +814,4 @@ In order to use Spring Data JDBC for ScalarDB, the following features are implem - [Spring Data JDBC - Reference Documentation](https://docs.spring.io/spring-data/jdbc/docs/3.0.x/reference/html/) - [ScalarDB JDBC Guide](jdbc-guide.mdx) -- [Javadoc for Spring Data JDBC for ScalarDB](https://javadoc.io/doc/com.scalar-labs/scalardb-sql-spring-data/3.13.1/index.html) +- [Javadoc for Spring Data JDBC for ScalarDB](https://javadoc.io/doc/com.scalar-labs/scalardb-sql-spring-data/3.13.2/index.html) diff --git a/versioned_docs/version-3.13/scalardb-sql/sql-api-guide.mdx b/versioned_docs/version-3.13/scalardb-sql/sql-api-guide.mdx index 8cabba75..0c3558be 100644 --- a/versioned_docs/version-3.13/scalardb-sql/sql-api-guide.mdx +++ b/versioned_docs/version-3.13/scalardb-sql/sql-api-guide.mdx @@ -111,7 +111,7 @@ ResultSet resultSet = sqlSession.execute(statement); ``` `Statement` objects can be built by `StatementBuilder` that has factory methods for corresponding SQLs. -Please see [the Javadoc of `StatementBuilder`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.1/com/scalar/db/sql/statement/builder/StatementBuilder.html) and [ScalarDB SQL Grammar](grammar.mdx) for more details. +Please see [the Javadoc of `StatementBuilder`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.2/com/scalar/db/sql/statement/builder/StatementBuilder.html) and [ScalarDB SQL Grammar](grammar.mdx) for more details. ### Handle ResultSet objects @@ -142,7 +142,7 @@ If you want to get the metadata of the `ResultSet` object, you can use the `getC ColumnDefinitions columnDefinitions = resultSet.getColumnDefinitions(); ``` -Please see [the Javadoc of `ColumnDefinitions`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.1/com/scalar/db/sql/ColumnDefinition.html) for more details. +Please see [the Javadoc of `ColumnDefinitions`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.2/com/scalar/db/sql/ColumnDefinition.html) for more details. ### Handle Record objects @@ -192,7 +192,7 @@ boolean isNullGottenByName = record.isNull(""); boolean isNullGottenByIndex = record.isNull(); ``` -Please see also [the Javadoc of `Record`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.1/com/scalar/db/sql/Record.html) for more details. +Please see also [the Javadoc of `Record`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.2/com/scalar/db/sql/Record.html) for more details. ### Prepared Statements @@ -237,7 +237,7 @@ preparedStatement2 .execute(); ``` -Please see also [the Javadoc of `PreparedStatement`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.1/com/scalar/db/sql/PreparedStatement.html) for more details. +Please see also [the Javadoc of `PreparedStatement`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.2/com/scalar/db/sql/PreparedStatement.html) for more details. ## Execute transactions @@ -351,10 +351,10 @@ You can get metadata with the `SqlSession.getMetadata()` method as follows: Metadata metadata = sqlSession.getMetadata(); ``` -Please see [the Javadoc of `Metadata`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.1/com/scalar/db/sql/metadata/Metadata.html) for the details. +Please see [the Javadoc of `Metadata`](https://javadoc.io/static/com.scalar-labs/scalardb-sql/3.13.2/com/scalar/db/sql/metadata/Metadata.html) for the details. ## References - [ScalarDB SQL Grammar](grammar.mdx) - [Two-phase Commit Transactions](../two-phase-commit-transactions.mdx) -- [Javadoc for ScalarDB SQL](https://javadoc.io/doc/com.scalar-labs/scalardb-sql/3.13.1/index.html) +- [Javadoc for ScalarDB SQL](https://javadoc.io/doc/com.scalar-labs/scalardb-sql/3.13.2/index.html)