This is an automated email from the ASF dual-hosted git repository.
ptupitsyn pushed a commit to branch ignite-2.9-docs
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/ignite-2.9-docs by this push:
new bc2f56d IGNITE-13615 Update .NET thin client feature set documentation
bc2f56d is described below
commit bc2f56d6e2c8731584a5a94155d3afa6dc15014f
Author: Pavel Tupitsyn <ptupit...@apache.org>
AuthorDate: Tue Nov 3 10:33:32 2020 +0300
IGNITE-13615 Update .NET thin client feature set documentation
---
docs/_docs/thin-client-comparison.csv | 6 +++---
docs/_docs/thin-clients/getting-started-with-thin-clients.adoc | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/_docs/thin-client-comparison.csv
b/docs/_docs/thin-client-comparison.csv
index ee2fe80..2e5fb45 100644
--- a/docs/_docs/thin-client-comparison.csv
+++ b/docs/_docs/thin-client-comparison.csv
@@ -7,9 +7,9 @@ Async Operations,No,{yes},No,{yes},{yes},{yes}
SSL/TLS,{yes},{yes},{yes},{yes},{yes},{yes}
Authentication,{yes},{yes},{yes},{yes},{yes},{yes}
Partition Awareness,{yes},{yes},{yes},{yes},{yes},No
-Failover,{yes},No,{yes},{yes},{yes},{yes}
+Failover,{yes},{yes},{yes},{yes},{yes},{yes}
Transactions,{yes},No,No,No,No,No
Cluster API,{yes},{yes},No,No,No,No
-Cluster discovery,No,{yes},No,No,No,No
Compute,{yes},{yes},No,No,No,No
-Service invocation,{yes},No,No,No,No,No
\ No newline at end of file
+Service invocation,{yes},No,No,No,No,No
+Server Discovery,No,{yes},No,No,No,No
\ No newline at end of file
diff --git a/docs/_docs/thin-clients/getting-started-with-thin-clients.adoc
b/docs/_docs/thin-clients/getting-started-with-thin-clients.adoc
index 7860bf4..5e0c37c 100644
--- a/docs/_docs/thin-clients/getting-started-with-thin-clients.adoc
+++ b/docs/_docs/thin-clients/getting-started-with-thin-clients.adoc
@@ -46,7 +46,7 @@ include::thin-client-comparison.csv[]
=== Client Connection Failover
-All thin clients (except for the .NET thin client) support a connection
failover mechanism, whereby the client automatically switches to an available
node in case of the current node or connection failure.
+All thin clients support a connection failover mechanism, whereby the client
automatically switches to an available node in case of the current node or
connection failure.
For this mechanism to work, you need to provide a list of node addresses you
want to use for failover purposes in the client configuration.
Refer to the specific client documentation for more details.
