diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc index e102653d0..4d22590cd 100644 --- a/docs/modules/ROOT/nav.adoc +++ b/docs/modules/ROOT/nav.adoc @@ -172,7 +172,7 @@ include::tiered-storage:partial$nav.adoc[] // Files need an overview (options, what's available for SQL, what's available for Jet API) ** xref:integrate:file-connector.adoc[] ** xref:integrate:legacy-file-connector.adoc[] -* Integrating with Spring +* Integrate with Spring ** xref:spring:overview.adoc[Overview] ** xref:spring:configuration.adoc[] ** xref:spring:springaware.adoc[] @@ -181,10 +181,10 @@ include::tiered-storage:partial$nav.adoc[] ** xref:spring:transaction-manager.adoc[] ** xref:spring:best-practices.adoc[] * xref:integrate:integrate-with-feast.adoc[] -** xref:integrate:install-connect.adoc[] +** xref:integrate:install-connect.adoc[Install and connect Feast] ** xref:integrate:feast-config.adoc[] -** xref:integrate:feature-engineering-with-feast.adoc[] -** xref:integrate:streaming-features-with-feast.adoc[] +** xref:integrate:feature-engineering-with-feast.adoc[Get started with Feast batch features] +** xref:integrate:streaming-features-with-feast.adoc[Get started with Feast streaming features] * xref:integrate:kafka-connect-connectors.adoc[] * Messaging System Connectors ** xref:integrate:messaging-system-connectors.adoc[Overview] diff --git a/docs/modules/clients/pages/cplusplus.adoc b/docs/modules/clients/pages/cplusplus.adoc index f43456413..4d341ba9e 100644 --- a/docs/modules/clients/pages/cplusplus.adoc +++ b/docs/modules/clients/pages/cplusplus.adoc @@ -2,6 +2,8 @@ :page-api-reference: http://hazelcast.github.io/hazelcast-cpp-client/{page-latest-supported-cplusplus-client}/index.html [[c-client]] +TIP: For the latest C{plus}{plus} API documentation, see http://hazelcast.github.io/hazelcast-cpp-client/{page-latest-supported-cplusplus-client}/index.html[Hazelcast C++ Client docs]. + You can use the native {cpp} client to connect to Hazelcast cluster members and perform almost all operations that a member can perform. Clients differ from members in that clients do not hold data. The {cpp} client is diff --git a/docs/modules/clients/pages/dotnet.adoc b/docs/modules/clients/pages/dotnet.adoc index e1e66424a..ab2159fde 100644 --- a/docs/modules/clients/pages/dotnet.adoc +++ b/docs/modules/clients/pages/dotnet.adoc @@ -2,6 +2,8 @@ :page-api-reference: http://hazelcast.github.io/hazelcast-csharp-client/{page-latest-supported-csharp-client}/api/index.html [[net-client]] +TIP: For the latest .NET API documentation, see http://hazelcast.github.io/hazelcast-csharp-client/{page-latest-supported-csharp-client}/api/index.html[Hazelcast .NET Client docs]. + You can use the native .NET client to connect to Hazelcast client members. The API is very similar to the Java native client. diff --git a/docs/modules/clients/pages/go.adoc b/docs/modules/clients/pages/go.adoc index 8a3fd2f0a..9d36ca59a 100644 --- a/docs/modules/clients/pages/go.adoc +++ b/docs/modules/clients/pages/go.adoc @@ -1,6 +1,8 @@ = Go Client :page-api-reference: https://pkg.go.dev/github.com/hazelcast/hazelcast-go-client@v{page-latest-supported-go-client} +TIP: For the latest Go API documentation, see https://pkg.go.dev/github.com/hazelcast/hazelcast-go-client@v{page-latest-supported-go-client}[Hazelcast Go Client docs]. + Go Client implementation for Hazelcast. It is implemented using the Hazelcast Open Binary Client Protocol. See Hazelcast Go client's GitHub https://github.com/hazelcast/hazelcast-go-client[repo^] diff --git a/docs/modules/clients/pages/java.adoc b/docs/modules/clients/pages/java.adoc index 4c3d04a44..63324e67d 100644 --- a/docs/modules/clients/pages/java.adoc +++ b/docs/modules/clients/pages/java.adoc @@ -4,6 +4,8 @@ :page-toclevels: 3 [[java-client]] +TIP: For the latest Java API documentation, see https://docs.hazelcast.org/docs/{page-latest-supported-java-client}/javadoc[Hazelcast Java Client docs]. + To get started, include the `hazelcast.jar` dependency in your classpath. Once included, you can start using this client as if you are using the Hazelcast API. The differences are discussed in the below sections. diff --git a/docs/modules/clients/pages/memcache.adoc b/docs/modules/clients/pages/memcache.adoc index b46c460e3..974afc0a8 100644 --- a/docs/modules/clients/pages/memcache.adoc +++ b/docs/modules/clients/pages/memcache.adoc @@ -1,12 +1,11 @@ = Memcache Client -NOTE: Hazelcast Memcache Client only supports ASCII protocol. Binary Protocol is not supported. - A Memcache client written in any language can talk directly to a Hazelcast cluster. No additional configuration is required. -To be able to use a Memcache client, you must enable -the Memcache client request listener service using either one of the following configuration options: +NOTE: Hazelcast Memcache Client only supports ASCII protocol. Binary Protocol is not supported. + +To be able to use a Memcache client, you must enable the Memcache client request listener service using either one of the following configuration options: 1 - Using the `network` configuration element: diff --git a/docs/modules/clients/pages/nodejs.adoc b/docs/modules/clients/pages/nodejs.adoc index e844e9d41..e90c3fd82 100644 --- a/docs/modules/clients/pages/nodejs.adoc +++ b/docs/modules/clients/pages/nodejs.adoc @@ -1,6 +1,8 @@ = Node.js Client :page-api-reference: http://hazelcast.github.io/hazelcast-nodejs-client/api/{page-latest-supported-nodejs-client}/docs/ +TIP: For the latest Node.js API documentation, see http://hazelcast.github.io/hazelcast-nodejs-client/api/{page-latest-supported-nodejs-client}/docs/[Hazelcast Node.js Client docs]. + Node.js Client implementation for Hazelcast. It is implemented using the Hazelcast Open Binary Client Protocol. See Hazelcast Node.js client's GitHub https://github.com/hazelcast/hazelcast-nodejs-client[repo^] diff --git a/docs/modules/clients/pages/python.adoc b/docs/modules/clients/pages/python.adoc index 83b5e9b63..00541ca77 100644 --- a/docs/modules/clients/pages/python.adoc +++ b/docs/modules/clients/pages/python.adoc @@ -1,6 +1,8 @@ = Python Client :page-api-reference: https://hazelcast.readthedocs.io/en/v{page-latest-supported-python-client}/index.html +TIP: For the latest Python API documentation, see https://hazelcast.readthedocs.io/en/v{page-latest-supported-python-client}/index.html[Hazelcast Python Client docs]. + Python Client implementation for Hazelcast. It is implemented using the Hazelcast Open Binary Client Protocol. See Hazelcast Python client's GitHub https://github.com/hazelcast/hazelcast-python-client[repo^] diff --git a/docs/modules/data-structures/partials/nav.adoc b/docs/modules/data-structures/partials/nav.adoc index 6c2f8cfd1..8ba296638 100644 --- a/docs/modules/data-structures/partials/nav.adoc +++ b/docs/modules/data-structures/partials/nav.adoc @@ -46,4 +46,4 @@ ** AI/ML Data Structures *** xref:data-structures:cardinality-estimator-service.adoc[] *** xref:data-structures:vector-collections.adoc[Vector Collection] -*** xref:data-structures:vector-search-overview.adoc[Data Structure Design] +**** xref:data-structures:vector-search-overview.adoc[Data Structure Design] diff --git a/docs/modules/integrate/pages/feature-engineering-with-feast.adoc b/docs/modules/integrate/pages/feature-engineering-with-feast.adoc index 9cc3e5cc1..8fd7a8c79 100644 --- a/docs/modules/integrate/pages/feature-engineering-with-feast.adoc +++ b/docs/modules/integrate/pages/feature-engineering-with-feast.adoc @@ -13,7 +13,7 @@ Finally, you will transfer the features in the offline store to the online store You will need the following ready before starting the tutorial: -* Hazelcast CLC. link:https://docs.hazelcast.com/clc/latest/install-clc[Installation instructions] +* Hazelcast CLC (see link:https://docs.hazelcast.com/clc/latest/install-clc[Install CLC]) * A recent version of Docker and Docker Compose To set up your project, complete the following steps: diff --git a/docs/modules/integrate/pages/integrate-with-feast.adoc b/docs/modules/integrate/pages/integrate-with-feast.adoc index 4c5464af7..612c9f96a 100644 --- a/docs/modules/integrate/pages/integrate-with-feast.adoc +++ b/docs/modules/integrate/pages/integrate-with-feast.adoc @@ -115,5 +115,5 @@ To use Feast with Hazelcast, you must do the following: You can also work through the following tutorials: -* Get Started with Feature Store -* Feature Compute and Transformation +* xref:integrate:feature-engineering-with-feast.adoc[Get started with Feast batch features] +* xref:integrate:streaming-features-with-feast.adoc[Get started with Feast streaming features] diff --git a/docs/modules/integrate/pages/streaming-features-with-feast.adoc b/docs/modules/integrate/pages/streaming-features-with-feast.adoc index 74d5119db..62e502b2b 100644 --- a/docs/modules/integrate/pages/streaming-features-with-feast.adoc +++ b/docs/modules/integrate/pages/streaming-features-with-feast.adoc @@ -12,7 +12,7 @@ Then update the online feature store using a Jet job in real time from transacti You will need the following ready before starting the tutorial: -* Hazelcast CLC - link:https://docs.hazelcast.com/clc/latest/install-clc[Installation instructions] +* Hazelcast CLC (see link:https://docs.hazelcast.com/clc/latest/install-clc[Install CLC]) * A recent version of Docker and Docker Compose To set up your project, complete the following steps: @@ -346,6 +346,7 @@ Outputs something similar to: ] } ---- + == Summary In this tutorial, you learned how to set up a feature engineering project that uses Hazelcast as the online store.