IGNITE-26733 Updating doc versioning to 3.1.0 (#6793)

Author: IgGusev

docs/_docs/administrators-guide/handling-exceptions.adoc

@@ -106,7 +106,7 @@ When the exception happens, Apache Ignite provides a UUID of the specific except
 |`IGN-TX-1`|Default error for transaction state storage.|General error, check the logs and take action depending on the cause. Make sure there are no disk errors.
 |`IGN-TX-2`|Storage is stopped.|Storage is stopped due to the node stop or replica stop. No action is required unless this behavior is unexpected. Otherwise check the log for details.
 |`IGN-TX-3`|Unexpected transaction state on state change.|This can happen when trying to commit an already aborted transaction or roll back a committed one. No action is required.
-|`IGN-TX-4`|Failed to acquire a lock on a key due to a conflict.|The lock is taken by another transaction. Retry the operation or change the deadlock prevention policy.
+|`IGN-TX-4`|Failed to acquire a lock on a key due to a conflict.|The lock is held by another transaction. Retry the operation or change the deadlock prevention policy.
 |`IGN-TX-5`|Failed to acquire a lock on a key within the timeout.|The lock is held by another transaction. Make sure that the other transaction is not hanging, kill it if necessary; or retry the operation.
 |`IGN-TX-6`|Failed to commit a transaction.|Take actions depending on the cause. Make sure that all partitions in the cluster have a majority of nodes online in their groups.
 |`IGN-TX-7`|Failed to roll back a transaction.|Take actions depending on the cause. Make sure that all partitions in the cluster have a majority of nodes online in their groups.

docs/_docs/administrators-guide/storage/data-partitions.adoc

@@ -120,4 +120,4 @@ NOTE: Reset is likely to result in <<Partition Rebalance>>, which may take a lon
 
 == Partition Rebalance
 
-When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.
+When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to the partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.

docs/_docs/administrators-guide/storage/engines/rocksdb.adoc

@@ -17,7 +17,7 @@
 
 WARNING: RocksDB support is experimental.
 
-RocksDB is a persistent storage engine based on LSM tree. It is best used in environments with a large number of write requests.
+RocksDB is a persistent storage engine based on an LSM tree. It is best used in environments with a large number of write requests.
 
 == Profile Configuration
 

docs/_docs/developers-guide/clients/dotnet.adoc

@@ -30,7 +30,7 @@ C# client is available via NuGet. To add it, use the `add package` command:
 
 [source, bash, subs="attributes,specialchars"]
 ----
-dotnet add package Apache.Ignite --version 3.0.0
+dotnet add package Apache.Ignite --version 3.1.0
 ----
 
 == Connecting to Cluster

docs/_docs/developers-guide/clients/java.adoc

@@ -33,7 +33,7 @@ Java client can be added to your project by using maven:
 <dependency>
     <groupId>org.apache.ignite</groupId>
     <artifactId>ignite-client</artifactId>
-    <version>3.0.0</version>
+    <version>3.1.0</version>
 </dependency>
 ----
 

docs/_docs/developers-guide/code-deployment/code-deployment.adoc

@@ -73,7 +73,7 @@ public class MyJob implements ComputeJob<String, String> {
 }
 ----
 
-You can manage deployment units using either link:ignite-cli-tool[CLI] commands or the link:https://ignite.apache.org/releases/3.0.0/openapi.yaml[REST API]. Both methods provide the same functionality for deploying, listing, and undeploying code.
+You can manage deployment units using either link:ignite-cli-tool[CLI] commands or the link:https://ignite.apache.org/releases/3.1.0/openapi.yaml[REST API]. Both methods provide the same functionality for deploying, listing, and undeploying code.
 
 == Deploying Units with Folder Structures
 
@@ -161,7 +161,7 @@ curl -X POST 'http://localhost:10300/management/v1/deployment/units/unit/1.0.0?i
 
 - You can target nodes using either the `deployMode` or `initialNodes` parameter. These options serve the same purpose as the similar CLI parameters, ensuring the unit propagates as needed.
 
-- For additional details see the corresponding link:https://ignite.apache.org/releases/3.0.0/openapi.yaml[API documentation].
+- For additional details see the corresponding link:https://ignite.apache.org/releases/3.1.0/openapi.yaml[API documentation].
 
 === Deploy Manually
 

docs/_docs/developers-guide/data-streamer.adoc

@@ -23,7 +23,7 @@ Data streaming provides at-least-once delivery guarantee.
 
 == Using Data Streamer API
 
-The link:https://ignite.apache.org/releases/3.0.0/javadoc/org/apache/ignite/table/DataStreamerTarget.html[Data Streamer API] lets you load large amounts of data into your cluster quickly and reliably using a publisher–subscriber model, where you create a publisher that streams your data entries to a table view, and the system distributes these entries across the cluster. You can configure how the data is processed via a `DataStreamerOptions` object that allows to set batch sizes, auto-flush intervals, retry limits.
+The link:https://ignite.apache.org/releases/3.1.0/javadoc/org/apache/ignite/table/DataStreamerTarget.html[Data Streamer API] lets you load large amounts of data into your cluster quickly and reliably using a publisher–subscriber model, where you create a publisher that streams your data entries to a table view, and the system distributes these entries across the cluster. You can configure how the data is processed via a `DataStreamerOptions` object that allows to set batch sizes, auto-flush intervals, retry limits.
 
 === Configuring Data Streamer
 
@@ -187,12 +187,12 @@ public record Account(int Id, string Name);
 The Apache Ignite 3 streaming API supports advanced streaming scenarios by allowing you to create a custom receiver that defines server-side processing logic. Use a receiver when you need to process or transform data on the server, update multiple tables from a single data stream, or work with incoming data that does not match a table schema.
 
 With a receiver, you can stream data in any format, as it is schema-agnostic.
-The receiver also has access to the full Ignite 3 API through the link:https://ignite.apache.org/releases/3.0.0/javadoc/org/apache/ignite/table/DataStreamerReceiverContext.html[`DataStreamerReceiverContext`].
+The receiver also has access to the full Ignite 3 API through the link:https://ignite.apache.org/releases/3.1.0/javadoc/org/apache/ignite/table/DataStreamerReceiverContext.html[`DataStreamerReceiverContext`].
 
 The data streamer controls data flow by requesting items only when partition buffers have space. `DataStreamerOptions.perPartitionParallelOperations` controls how many buffers can be allocated per partition. When buffers are full, the streamer stops requesting more data until some items are processed.
 Additionally, if a `resultSubscriber` is specified, it also applies backpressure on the streamer. If the subscriber is slow at consuming results, the streamer reduces its request rate from the publisher accordingly.
 
-To use a receiver, you need to implement the link:https://ignite.apache.org/releases/3.0.0/javadoc/org/apache/ignite/table/DataStreamerReceiver.html[`DataStreamerReceiver`] interface. The receiver’s `receive` method processes each batch of items streamed to the server, so you can apply custom logic and return results for each item as needed:
+To use a receiver, you need to implement the link:https://ignite.apache.org/releases/3.1.0/javadoc/org/apache/ignite/table/DataStreamerReceiver.html[`DataStreamerReceiver`] interface. The receiver's `receive` method processes each batch of items streamed to the server, so you can apply custom logic and return results for each item as needed:
 
 [tabs]
 --
@@ -605,7 +605,7 @@ await Task.Yield(); // Simulate async data source.
 
 ==== Custom Marshallers in .NET
 
-In .NET, you can define custom marshallers by implementing the link:https://ignite.apache.org/releases/3.0.0/dotnetdoc/api/Apache.Ignite.Marshalling.IMarshaller-1.html[`IMarshaller`] interface.
+In .NET, you can define custom marshallers by implementing the link:https://ignite.apache.org/releases/3.1.0/dotnetdoc/api/Apache.Ignite.Marshalling.IMarshaller-1.html[`IMarshaller`] interface.
 
 For example, the code below demonstrates how to use `JsonMarshaller` to serialize data, arguments, and results.
 

docs/_docs/developers-guide/events/overview.adoc

@@ -37,7 +37,7 @@ cluster config update ignite.eventlog.sinks.exampleSink = {type="log", channel="
 Now, the authorization events will be written to the log. Here is how the event may look like:
 
 ----
-2024-06-04 16:19:29:840 +0300 [INFO][%defaultNode%sql-execution-pool-1][EventLog] {"type":"USER_AUTHORIZATION_SUCCESS","timestamp":1717507169840,"productVersion":"3.0.0","user":{"username":"ignite","authenticationProvider":"basic"},"fields":{"privileges":[{"action":"CREATE_TABLE","on":{"objectType":"TABLE","objectName":"TEST2","schema":"PUBLIC"}}],"roles":["system"]}}
+2024-06-04 16:19:29:840 +0300 [INFO][%defaultNode%sql-execution-pool-1][EventLog] {"type":"USER_AUTHORIZATION_SUCCESS","timestamp":1717507169840,"productVersion":"3.1.0","user":{"username":"ignite","authenticationProvider":"basic"},"fields":{"privileges":[{"action":"CREATE_TABLE","on":{"objectType":"TABLE","objectName":"TEST2","schema":"PUBLIC"}}],"roles":["system"]}}
 ----
 
 Below is the cluster configuration config in JSON.
@@ -145,7 +145,7 @@ All events in Apache Ignite 3 follow the same basic structure described below. S
   "type": "AUTHENTICATION",
   "user": { "username": "John", "authenticationProvider": "basic" },
   "timestamp": 1715169617,
-  "productVersion": "3.0.0",
+  "productVersion": "3.1.0",
   "fields": {}
 }
 ----

docs/_docs/developers-guide/sql/jdbc-driver.adoc

@@ -34,7 +34,7 @@ The JDBC connector needs to be included from Maven:
 <dependency>
     <groupId>org.apache.ignite</groupId>
     <artifactId>ignite-jdbc</artifactId>
-    <version>3.0.0</version>
+    <version>3.1.0</version>
 </dependency>
 ----
 

docs/_docs/developers-guide/sql/odbc/querying-modifying-data.adoc

@@ -57,13 +57,13 @@ SQLCHAR query1[] = "CREATE TABLE Person ( "
     "id LONG PRIMARY KEY, "
     "firstName VARCHAR, "
     "lastName VARCHAR, "
-    "salary FLOAT) "";
+    "salary FLOAT)";
 
 SQLExecDirect(stmt, query1, SQL_NTS);
 
 SQLCHAR query2[] = "CREATE TABLE Organization ( "
     "id LONG PRIMARY KEY, "
-    "name VARCHAR) "";
+    "name VARCHAR)";
 
 SQLExecDirect(stmt, query2, SQL_NTS);