Uniquify anchor links to fix asciidoc/docbook generation

docs/reference/analysis/icu-plugin.asciidoc

@@ -60,7 +60,7 @@ normally be left out. Sample setting:
 --------------------------------------------------
 
 [float]
-[[filtering]]
+[[icu-filtering]]
 ==== Filtering
 
 The folding can be filtered by a set of unicode characters with the

docs/reference/cluster/update-settings.asciidoc

@@ -48,7 +48,7 @@ curl -XGET localhost:9200/_cluster/settings
 There is a specific list of settings that can be updated, those include:
 
 [float]
-[[settings]]
+[[cluster-settings]]
 === Cluster settings
 
 [float]
@@ -142,7 +142,7 @@ There is a specific list of settings that can be updated, those include:
      See <<modules-threadpool>>
 
 [float]
-[[index-settings]]
+[[cluster-index-settings]]
 === Index settings
 
 [float]

docs/reference/docs/bulk.asciidoc

@@ -85,7 +85,7 @@ If using the HTTP API, make sure that the client does not send HTTP
 chunks, as this will slow things down.
 
 [float]
-[[versioning]]
+[[bulk-versioning]]
 === Versioning
 
 Each bulk item can include the version value using the
@@ -95,7 +95,7 @@ support the `version_type`/`_version_type` when using `external`
 versioning.
 
 [float]
-[[routing]]
+[[bulk-routing]]
 === Routing
 
 Each bulk item can include the routing value using the
@@ -110,7 +110,7 @@ Each bulk index action can include a percolate value using the
 `_percolate`/`percolate` field.
 
 [float]
-[[parent]]
+[[bulk-parent]]
 === Parent
 
 Each bulk item can include the parent value using the `_parent`/`parent`
@@ -118,7 +118,7 @@ field. It automatically follows the behavior of the index / delete
 operation based on the `_parent` / `_routing` mapping.
 
 [float]
-[[timestamp]]
+[[bulk-timestamp]]
 === Timestamp
 
 Each bulk item can include the timestamp value using the
@@ -126,7 +126,7 @@ Each bulk item can include the timestamp value using the
 the index operation based on the `_timestamp` mapping.
 
 [float]
-[[ttl]]
+[[bulk-ttl]]
 === TTL
 
 Each bulk item can include the ttl value using the `_ttl`/`ttl` field.
@@ -134,7 +134,7 @@ It automatically follows the behavior of the index operation based on
 the `_ttl` mapping.
 
 [float]
-[[consistency]]
+[[bulk-consistency]]
 === Write Consistency
 
 When making bulk calls, you can require a minimum number of active
@@ -150,7 +150,7 @@ will need to be a single shard active (in this case, `one` and `quorum`
 is the same).
 
 [float]
-[[refresh]]
+[[bulk-refresh]]
 === Refresh
 
 The `refresh` parameter can be set to `true` in order to refresh the

docs/reference/docs/delete-by-query.asciidoc

@@ -77,7 +77,7 @@ $ curl -XDELETE 'http://localhost:9200/_all/_query?q=tag:wow'
 --------------------------------------------------
 
 [float]
-[[parameters]]
+[[delete-by-query-parameters]]
 === Request Parameters
 
 When executing a delete by query using the query parameter `q`, the
@@ -106,14 +106,14 @@ executed and delete all documents. The body content can also be passed
 as a REST parameter named `source`.
 
 [float]
-[[distributed]]
+[[delete-by-query-distributed]]
 === Distributed
 
 The delete by query API is broadcast across all primary shards, and from
 there, replicated across all shards replicas.
 
 [float]
-[[routing]]
+[[delete-by-query-routing]]
 === Routing
 
 The routing value (a comma separated list of the routing values) can be
@@ -130,7 +130,7 @@ the primary shard). The `replication` parameter can be set to `async`
 (defaults to `sync`) in order to enable it.
 
 [float]
-[[consistency]]
+[[delete-by-query-consistency]]
 === Write Consistency
 
 Control if the operation will be allowed to execute based on the number

docs/reference/docs/delete.asciidoc

@@ -25,7 +25,7 @@ The result of the above delete operation is:
 --------------------------------------------------
 
 [float]
-[[versioning]]
+[[delete-versioning]]
 === Versioning
 
 Each document indexed is versioned. When deleting a document, the
@@ -34,7 +34,7 @@ trying to delete is actually being deleted and it has not changed in the
 meantime.
 
 [float]
-[[routing]]
+[[delete-routing]]
 === Routing
 
 When indexing using the ability to control the routing, in order to
@@ -56,7 +56,7 @@ no routing value is specified, the delete will be broadcasted
 automatically to all shards.
 
 [float]
-[[parent]]
+[[delete-parent]]
 === Parent
 
 The `parent` parameter can be set, which will basically be the same as
@@ -69,7 +69,7 @@ index with the automatically generated (and indexed)
 field _parent, which is in the format parent_type#parent_id.
 
 [float]
-[[index-creation]]
+[[delete-index-creation]]
 === Automatic index creation
 
 The delete operation automatically creates an index if it has not been
@@ -80,7 +80,7 @@ before (check out the <<indices-put-mapping,put mapping>>
 API for manually creating type mapping).
 
 [float]
-[[distributed]]
+[[delete-distributed]]
 === Distributed
 
 The delete operation gets hashed into a specific shard id. It then gets
@@ -88,7 +88,7 @@ redirected into the primary shard within that id group, and replicated
 (if needed) to shard replicas within that id group.
 
 [float]
-[[replication]]
+[[delete-replication]]
 === Replication Type
 
 The replication of the operation can be done in an asynchronous manner
@@ -97,7 +97,7 @@ the primary shard). The `replication` parameter can be set to `async`
 (defaults to `sync`) in order to enable it.
 
 [float]
-[[consistency]]
+[[delete-consistency]]
 === Write Consistency
 
 Control if the operation will be allowed to execute based on the number
@@ -113,7 +113,7 @@ will need to be a single shard active (in this case, `one` and `quorum`
 is the same).
 
 [float]
-[[refresh]]
+[[delete-refresh]]
 === Refresh
 
 The `refresh` parameter can be set to `true` in order to refresh the

docs/reference/docs/get.asciidoc

@@ -66,7 +66,7 @@ The get API allows for `_type` to be optional. Set it to `_all` in order
 to fetch the first document matching the id across all types.
 
 [float]
-[[fields]]
+[[get-fields]]
 === Fields
 
 The get operation allows specifying a set of fields that will be
@@ -104,7 +104,7 @@ curl -XHEAD 'http://localhost:9200/twitter/tweet/1/_source'
 --------------------------------------------------
 
 [float]
-[[routing]]
+[[get-routing]]
 === Routing
 
 When indexing using the ability to control the routing, in order to get
@@ -145,7 +145,7 @@ Custom (string) value::
 	user name.
 
 [float]
-[[refresh]]
+[[get-refresh]]
 === Refresh
 
 The `refresh` parameter can be set to `true` in order to refresh the
@@ -155,7 +155,7 @@ this does not cause a heavy load on the system (and slows down
 indexing).
 
 [float]
-[[distributed]]
+[[get-distributed]]
 === Distributed
 
 The get operation gets hashed into a specific shard id. It then gets

docs/reference/docs/index_.asciidoc

@@ -70,7 +70,7 @@ for example, set `action.auto_create_index` to `+aaa*,-bbb*,+ccc*,-*` (+
 meaning allowed, and - meaning disallowed).
 
 [float]
-[[versioning]]
+[[index-versioning]]
 === Versioning
 
 Each indexed document is given a version number. The associated
@@ -179,7 +179,7 @@ The result of the above index operation is:
 --------------------------------------------------
 
 [float]
-[[routing]]
+[[index-routing]]
 === Routing
 
 By default, shard placement — or `routing` — is controlled by using a
@@ -225,7 +225,7 @@ to be the same as it's parent, unless the routing value is explicitly
 specified using the `routing` parameter.
 
 [float]
-[[timestamp]]
+[[index-timestamp]]
 === Timestamp
 
 A document can be indexed with a `timestamp` associated with it. The
@@ -247,7 +247,7 @@ processed by the indexing chain. More information can be found on the
 page>>.
 
 [float]
-[[ttl]]
+[[index-ttl]]
 === TTL
 
 A document can be indexed with a `ttl` (time to live) associated with
@@ -321,7 +321,7 @@ cuts down on parsing overhead, as the parse tree for the document is
 simply re-used for percolation.
 
 [float]
-[[distributed]]
+[[index-distributed]]
 === Distributed
 
 The index operation is directed to the primary shard based on its route
@@ -330,7 +330,7 @@ containing this shard. After the primary shard completes the operation,
 if needed, the update is distributed to applicable replicas.
 
 [float]
-[[consistency]]
+[[index-consistency]]
 === Write Consistency
 
 To prevent writes from taking place on the "wrong" side of a network
@@ -343,7 +343,7 @@ parameter can be used.
 Valid write consistency values are `one`, `quorum`, and `all`.
 
 [float]
-[[replication]]
+[[index-replication]]
 === Asynchronous Replication
 
 By default, the index operation only returns after all shards within the
@@ -354,7 +354,7 @@ When asynchronous replication is used, the index operation will return
 as soon as the operation succeeds on the primary shard.
 
 [float]
-[[refresh]]
+[[index-refresh]]
 === Refresh
 
 To refresh the index immediately after the operation occurs, so that the

docs/reference/docs/multi-get.asciidoc

@@ -71,7 +71,7 @@ curl 'localhost:9200/test/type/_mget' -d '{
 --------------------------------------------------
 
 [float]
-[[fields]]
+[[mget-fields]]
 === Fields
 
 Specific fields can be specified to be retrieved per document to get.

docs/reference/index-modules.asciidoc

@@ -9,7 +9,7 @@ all the relevant modules settings can be provided when creating an index
 (and it is actually the recommended way to configure an index).
 
 [float]
-[[settings]]
+[[index-modules-settings]]
 == Index Settings
 
 There are specific index level settings that are not associated with any

docs/reference/index-modules/allocation.asciidoc

@@ -2,7 +2,7 @@
 == Index Shard Allocation
 
 [float]
-[[filtering]]
+[[shard-allocation-filtering]]
 === Shard Allocation Filtering
 
 Allow to control allocation if indices on nodes based on include/exclude

docs/reference/index-modules/codec.asciidoc

@@ -11,7 +11,7 @@ using the builtin postings formats will suite your needs as is described
 in the <<mapping-core-types,mapping section>>
 
 [float]
-[[postings]]
+[[custom-postings]]
 === Configuring a custom postings format
 
 Custom postings format can be defined in the index settings in the

docs/reference/index-modules/fielddata.asciidoc

@@ -25,7 +25,7 @@ example, can be set to `5m` for a 5 minute expiry.
 |=======================================================================
 
 [float]
-[[filtering]]
+[[field-data-filtering]]
 === Filtering fielddata
 
 It is possible to control which field values are loaded into memory,
@@ -123,7 +123,7 @@ The `frequency` and `regex` filters can be combined:
 --------------------------------------------------
 
 [float]
-[[monitoring]]
+[[field-data-monitoring]]
 === Monitoring field data
 
 You can monitor memory usage for field data using

docs/reference/index-modules/similarity.asciidoc

@@ -48,7 +48,7 @@ Here we configure the DFRSimilarity so it can be referenced as
 === Available similarities
 
 [float]
-[[default]]
+[[default-similarity]]
 ==== Default similarity
 
 The default similarity that is based on the TF/IDF model. This
@@ -122,7 +122,7 @@ based model] . This similarity has the following options:
 Type name: `IB`
 
 [float]
-[[default]]
+[[default-base]]
 ==== Default and Base Similarities
 
 By default, Elasticsearch will use whatever similarity is configured as

docs/reference/index-modules/store.asciidoc

@@ -20,7 +20,7 @@ own consequences) for storing the index in memory.
 
 
 [float]
-[[throttling]]
+[[store-throttling]]
 === Store Level Throttling
 
 The way Lucene, the IR library elasticsearch uses under the covers,
@@ -91,7 +91,7 @@ process equal to the size of the file being mapped. Before using this
 class, be sure your have plenty of virtual address space.
 
 [float]
-[[memory]]
+[[store-memory]]
 === Memory
 
 The `memory` type stores the index in main memory with the following

docs/reference/indices/aliases.asciidoc

@@ -91,7 +91,7 @@ curl -XPOST 'http://localhost:9200/_aliases' -d '
 --------------------------------------------------
 
 [float]
-[[routing]]
+[[aliases-routing]]
 ==== Routing
 
 It is possible to associate routing values with aliases. This feature
@@ -152,7 +152,7 @@ curl -XGET 'http://localhost:9200/alias2/_search?q=user:kimchy&routing=2,3'
 --------------------------------------------------
 
 [float]
-[[adding]]
+[[alias-adding]]
 === Add a single index alias
 
 There is also an api to add a single index alias, with options: 
@@ -208,7 +208,7 @@ curl -XDELETE 'localhost:9200/users/_alias/user_12'
 --------------------------------------------------
 
 [float]
-[[retrieving]]
+[[alias-retrieving]]
 === Retrieving existing aliases
 
 The get index alias api allows to filter by

docs/reference/indices/create-index.asciidoc

@@ -73,7 +73,7 @@ curl -XPOST localhost:9200/test -d '{
 --------------------------------------------------
 
 [float]
-[[settings]]
+[[create-index-settings]]
 === Index Settings
 
 For more information regarding all the different index level settings

docs/reference/indices/optimize.asciidoc

@@ -13,7 +13,7 @@ $ curl -XPOST 'http://localhost:9200/twitter/_optimize'
 --------------------------------------------------
 
 [float]
-[[parameters]]
+[[optimize-parameters]]
 === Request Parameters
 
 The optimize API accepts the following request parameters:
@@ -37,7 +37,7 @@ to `true`. Note, a merge can potentially be a very heavy operation, so
 it might make sense to run it set to `false`.
 
 [float]
-[[multi-index]]
+[[optimize-multi-index]]
 === Multi Index
 
 The optimize API can be applied to more than one index with a single

docs/reference/indices/put-mapping.asciidoc

@@ -41,7 +41,7 @@ conflict. New mapping definitions can be added to object types, and core
 type mapping can be upgraded to `multi_field` type.
 
 [float]
-[[multi-index]]
+[[put-mapping-multi-index]]
 === Multi Index
 
 The put mapping API can be applied to more than one index with a single

docs/reference/indices/update-settings.asciidoc

@@ -187,7 +187,7 @@ curl -XPOST 'http://localhost:9200/test/_optimize?max_num_segments=5'
 --------------------------------------------------
 
 [float]
-[[analysis]]
+[[update-settings-analysis]]
 === Updating Index Analysis
 
 It is also possible to define new <<analysis,analyzers>> for the index.

docs/reference/indices/warmers.asciidoc

@@ -66,7 +66,7 @@ curl -XPUT localhost:9200/_template/template_1 -d '
 --------------------------------------------------
 
 [float]
-[[adding]]
+[[warmer-adding]]
 === Put Warmer
 
 Allows to put a warmup search request on a specific index (or indices),
@@ -133,7 +133,7 @@ curl -XDELETE localhost:9200/test/_warmer/
 --------------------------------------------------
 
 [float]
-[[retrieving]]
+[[warmer-retrieving]]
 === GETting Warmer
 
 Getting a warmer for specific index (or alias, or several indices) based

docs/reference/mapping.asciidoc

@@ -17,7 +17,7 @@ no performance overhead) and have sensible defaults. Only when the
 defaults need to be overridden must a mapping definition be provided.
 
 [float]
-[[mapping-types]]
+[[all-mapping-types]]
 === Mapping Types
 
 Mapping types are a way to divide the documents in an index into logical

docs/reference/modules/indices.asciidoc

@@ -24,7 +24,7 @@ lower limit for the memory allocated per shard for its own indexing
 buffer. It defaults to `4mb`.
 
 [float]
-[[ttl]]
+[[indices-ttl]]
 === TTL interval
 
 You can dynamically set the `indices.ttl.interval` allows to set how

docs/reference/modules/plugins.asciidoc

@@ -129,7 +129,7 @@ plugin --remove head --silent
 === Known Plugins
 
 [float]
-[[analysis]]
+[[analysis-plugins]]
 ==== Analysis Plugins
 
 .Supported by Elasticsearch

docs/reference/search.asciidoc

@@ -4,7 +4,6 @@
 [partintro]
 --
 ["float",id="search-multi-index"]
-[[multiple-indices]]
 == Multiple Indices
 
 All search APIs support execution across multiple indices, using simple
@@ -17,7 +16,7 @@ All multi indices API support the `ignore_indices` option. Setting it to
 execution. By default, when its not set, the request will fail. 
 
 [float]
-[[routing]]
+[[search-routing]]
 == Routing
 
 When executing a search, it will be broadcasted to all the index/indices

docs/reference/search/request/highlighting.asciidoc

@@ -168,7 +168,7 @@ is required. Note that `fragment_size` is ignored in this case.
 When using `fast-vector-highlighter` one can use `fragment_offset`
 parameter to control the margin to start highlighting from.
 
-[[settings]]
+[[highlighting-settings]]
 ==== Global Settings
 
 Highlighting settings can be set on a global level and then overridden

docs/reference/search/suggesters/completion-suggest.asciidoc

@@ -27,7 +27,7 @@ documents. The `completion` suggester circumvents this by storing the
 FST as part of your index during index time. This allows for really fast
 loads and executions.
 
-[[mapping]]
+[[completion-suggester-mapping]]
 ==== Mapping
 
 In order to use this feature, you have to specify a special mapping for

docs/reference/setup/configuration.asciidoc

@@ -39,8 +39,8 @@ In order to test how many open files the process can open, start it with
 `-Des.max-open-files` set to `true`. This will print the number of open
 files the process can open on startup.
 
-["float",id="setup-configuration-memory"]
-[[memory]]
+[float]
+[[setup-configuration-memory]]
 ==== Memory Settings
 
 There is an option to use
@@ -181,7 +181,7 @@ $ elasticsearch -f -Des.config=/path/to/config/file
 --------------------------------------------------
 
 [float]
-[[index-settings]]
+[[configuration-index-settings]]
 === Index Settings
 
 Indices created within the cluster can provide their own settings. For