[GitHub] [ignite] timoninmaxim commented on a diff in pull request #10348: IGNITE-17321 Document which api can work with partition awareness

[GitBox <gi...@apache.org>]

timoninmaxim commented on code in PR #10348:
URL: https://github.com/apache/ignite/pull/10348#discussion_r1039218667


##########
modules/core/src/main/java/org/apache/ignite/configuration/ClientConfiguration.java:
##########
@@ -525,6 +525,9 @@ public ClientConfiguration setTransactionConfiguration(ClientTransactionConfigur
     }
 
     /**
+     * Used only whith a single key operations API without explicit transactions

Review Comment:
   Here and below - misprint in "whith"



##########
docs/_docs/includes/partition-awareness.adoc:
##########
@@ -25,6 +25,8 @@ Notice how queries must pass through the proxy server node, where they are route
 With partition awareness in place, the thin client can directly route queries and operations to the primary nodes that own the data required for the queries.
 This eliminates the bottleneck, allowing the application to scale more easily.
 
+NOTE: This functionality works for a single key operations API without explicit ⁣ ⁣transactions (initiated via org.apache.ignite.client.ClientTransactions#txStart()). But for different platforms, the functionality may differ, for example, for java there is an implementation ScanQuery/IndexQuery with specified part.

Review Comment:
   "explicit  transactions" - there are 2 whitespaces. 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org