DATAREDIS-1121 - Add missing reference documentation anchors.

src/main/asciidoc/reference/introduction.adoc

@@ -1,4 +1,5 @@
 [float]
+[[introduction.structure]]
 = Document structure
 
 This part of the reference documentation explains the core functionality offered by Spring Data Redis.

src/main/asciidoc/reference/reactive-redis.adoc

@@ -165,6 +165,7 @@ public class Example {
 
 include::{referenceDir}/reactive-messaging.adoc[leveloffset=+1]
 
+[[redis:reactive:scripting]]
 == Reactive Scripting
 
 Executing Redis scripts via the reactive infrastructure can be done using the `ReactiveScriptExecutor` accessed best via `ReactiveRedisTemplate`.

src/main/asciidoc/reference/redis-cluster.adoc

@@ -65,6 +65,7 @@ public class AppConfig {
 
 NOTE: The initial configuration points driver libraries to an initial set of cluster nodes. Changes resulting from live cluster reconfiguration are kept only in the native driver and are not written back to the configuration.
 
+[[cluster.working.with.cluster]]
 == Working With Redis Cluster Connection
 
 As mentioned earlier, Redis Cluster behaves differently from single-node Redis or even a Sentinel-monitored master-replica environment. This is because the automatic sharding maps a key to one of 16384 slots, which are distributed across the nodes. Therefore, commands that involve more than one key must assert all keys map to the exact same slot to avoid cross-slot execution errors.
@@ -148,6 +149,7 @@ connection.mGet("thing1", "thing2");                                           <
 
 TIP: The preceding examples demonstrate the general strategy followed by Spring Data Redis. Be aware that some operations might require loading huge amounts of data into memory to compute the desired command. Additionally, not all cross-slot requests can safely be ported to multiple single slot requests and error if misused (for example, `PFCOUNT`).
 
+[[cluster.redistemplate]]
 == Working with `RedisTemplate` and `ClusterOperations`
 
 See the <<redis:template>> section for information about the general purpose, configuration, and usage of `RedisTemplate`.

src/main/asciidoc/reference/redis-repositories.adoc

@@ -796,6 +796,7 @@ class RepositoryClient {
 
 A Redis Repository requires `RedisKeyValueAdapter` and `RedisKeyValueTemplate` instances. These beans are created and managed by the Spring Data CDI extension if no provided beans are found. You can, however, supply your own beans to configure the specific properties of `RedisKeyValueAdapter` and `RedisKeyValueTemplate`.
 
+[[redis.repositories.anatomy]]
 == Redis Repositories Anatomy
 
 Redis as a store itself offers a very narrow low-level API leaving higher level functions, such as secondary indexes and
@@ -826,6 +827,7 @@ public class Address {
 ----
 ====
 
+[[redis.repositories.anatomy.insert]]
 === Insert new
 
 ====
@@ -847,6 +849,7 @@ SADD  "people:19315449-cda2-4f5c-b696-9cb8018fa1f9:idx" "people:firstname:rand"
 <4> Add the index of <3> to the set of helper structures for entry to keep track of indexes to clean on delete/update.
 ====
 
+[[redis.repositories.anatomy.replace]]
 === Replace existing
 
 ====
@@ -878,6 +881,7 @@ SADD      "people:e82908cf-e7d3-47c2-9eec-b4e0967ad0c9:idx" "people:firstname:Dr
 <9> Add the index of <6> to the set of helper structures for entry to keep track of indexes to clean on delete/update.
 ====
 
+[[redis.repositories.anatomy.geo]]
 === Save Geo Data
 
 Geo indexes follow the same rules as normal text based ones but use geo structure to store values. Saving an entity that
@@ -893,6 +897,7 @@ SADD   "people:76900e94-b057-44bc-abcf-8126d51a621b:idx" "people:hometown:locati
 <2> Keep track of the index structure.
 ====
 
+[[redis.repositories.anatomy.index]]
 === Find using simple index
 
 ====
@@ -911,6 +916,7 @@ HGETALL ...
 <2> Fetch each key returned by <1> individually.
 ====
 
+[[redis.repositories.anatomy.geo-index]]
 === Find using Geo Index
 
 ====