[DOCS] Add anchors for Asciidoctor migration (#41648)

Author: jrodewig

docs/reference/aggregations/bucket/diversified-sampler-aggregation.asciidoc

@@ -144,6 +144,7 @@ Please note that Elasticsearch will ignore the choice of execution hint if it is
 
 ==== Limitations
 
+[[div-sampler-breadth-first-nested-agg]]
 ===== Cannot be nested under `breadth_first` aggregations
 Being a quality-based filter the sampler aggregation needs access to the relevance score produced for each document.
 It therefore cannot be nested under a `terms` aggregation which has the `collect_mode` switched from the default `depth_first` mode to `breadth_first` as this discards scores.
@@ -152,6 +153,7 @@ In this situation an error will be thrown.
 ===== Limited de-dup logic.
 The de-duplication logic in the diversify settings applies only at a shard level so will not apply across shards.
 
+[[spec-syntax-geo-date-fields]]
 ===== No specialized syntax for geo/date fields
 Currently the syntax for defining the diversifying values is defined by a choice of `field` or
 `script` - there is no added syntactical sugar for expressing geo or date units such as "7d" (7

docs/reference/aggregations/bucket/filters-aggregation.asciidoc

@@ -118,6 +118,7 @@ request.  The response for this example would be:
 // TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
 // TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
 
+[[other-bucket]]
 ==== `Other` Bucket
 
 The `other_bucket` parameter can be set to add a bucket to the response which will contain all documents that do 

docs/reference/aggregations/bucket/sampler-aggregation.asciidoc

@@ -70,6 +70,7 @@ The default value is 100.
 
 ==== Limitations
 
+[[sampler-breadth-first-nested-agg]]
 ===== Cannot be nested under `breadth_first` aggregations
 Being a quality-based filter the sampler aggregation needs access to the relevance score produced for each document.
 It therefore cannot be nested under a `terms` aggregation which has the `collect_mode` switched from the default `depth_first` mode to `breadth_first` as this discards scores.

docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc

@@ -370,6 +370,7 @@ Available parameters in the script are
 `_subset_size`:: Number of documents in the subset.
 `_superset_size`:: Number of documents in the superset.
 
+[[sig-terms-shard-size]]
 ===== Size & Shard Size
 
 The `size` parameter can be set to define how many term buckets should be returned out of the overall terms list. By

docs/reference/aggregations/pipeline/avg-bucket-aggregation.asciidoc

@@ -6,6 +6,7 @@ experimental[]
 A sibling pipeline aggregation which calculates the (mean) average value of a specified metric in a sibling aggregation.
 The specified metric must be numeric and the sibling aggregation must be a multi-bucket aggregation.
 
+[[avg-bucket-agg-syntax]]
 ==== Syntax
 
 An `avg_bucket` aggregation looks like this in isolation:
@@ -19,7 +20,9 @@ An `avg_bucket` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[avg-bucket-params]]
 .`avg_bucket` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to find the average for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/bucket-script-aggregation.asciidoc

@@ -6,6 +6,7 @@ experimental[]
 A parent pipeline aggregation which executes a script which can perform per bucket computations on specified metrics
 in the parent multi-bucket aggregation. The specified metric must be numeric and the script must return a numeric value.
 
+[[bucket-script-agg-syntax]]
 ==== Syntax
 
 A `bucket_script` aggregation looks like this in isolation:
@@ -25,8 +26,9 @@ A `bucket_script` aggregation looks like this in isolation:
 <1> Here, `my_var1` is the name of the variable for this buckets path to use in the script, `the_sum` is the path to
 the metrics to use for that variable.
 
-
+[[bucket-script-params]]
 .`bucket_script` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`script` |The script to run for this aggregation. The script can be inline, file or indexed. (see <<modules-scripting>>

docs/reference/aggregations/pipeline/bucket-selector-aggregation.asciidoc

@@ -30,8 +30,9 @@ A `bucket_selector` aggregation looks like this in isolation:
 <1> Here, `my_var1` is the name of the variable for this buckets path to use in the script, `the_sum` is the path to
 the metrics to use for that variable.
 
-
+[[bucket-selector-params]]
 .`bucket_selector` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`script` |The script to run for this aggregation. The script can be inline, file or indexed. (see <<modules-scripting>>

docs/reference/aggregations/pipeline/cumulative-sum-aggregation.asciidoc

@@ -20,7 +20,9 @@ A `cumulative_sum` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[cumulative-sum-params]]
 .`cumulative_sum` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to find the cumulative sum for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/derivative-aggregation.asciidoc

@@ -18,7 +18,9 @@ A `derivative` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[derivative-params]]
 .`derivative` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to find the derivative for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/extended-stats-bucket-aggregation.asciidoc

@@ -21,7 +21,9 @@ A `extended_stats_bucket` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[extended-stats-bucket-params]]
 .`extended_stats_bucket` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to calculate stats for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/max-bucket-aggregation.asciidoc

@@ -20,7 +20,9 @@ A `max_bucket` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[max-bucket-params]]
 .`max_bucket` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to find the maximum for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/min-bucket-aggregation.asciidoc

@@ -20,7 +20,9 @@ A `max_bucket` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[min-bucket-params]]
 .`min_bucket` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to find the minimum for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/percentiles-bucket-aggregation.asciidoc

@@ -19,7 +19,10 @@ A `percentiles_bucket` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+
+[[sum-bucket-params]]
 .`sum_bucket` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to find the sum for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/serial-diff-aggregation.asciidoc

@@ -47,7 +47,9 @@ A `serial_diff` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[serial-diff-params]]
 .`serial_diff` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |Path to the metric of interest (see <<buckets-path-syntax, `buckets_path` Syntax>> for more details |Required |

docs/reference/aggregations/pipeline/stats-bucket-aggregation.asciidoc

@@ -19,7 +19,9 @@ A `stats_bucket` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[stats-bucket-params]]
 .`stats_bucket` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to calculate stats for (see <<buckets-path-syntax>> for more

docs/reference/aggregations/pipeline/sum-bucket-aggregation.asciidoc

@@ -19,7 +19,9 @@ A `sum_bucket` aggregation looks like this in isolation:
 }
 --------------------------------------------------
 
+[[sum-bucket-params]]
 .`sum_bucket` Parameters
+[options="header"]
 |===
 |Parameter Name |Description |Required |Default Value
 |`buckets_path` |The path to the buckets we wish to find the sum for (see <<buckets-path-syntax>> for more

docs/reference/docs/refresh.asciidoc

@@ -63,6 +63,7 @@ general, if you have a running system you don't wish to disturb then
 `refresh=wait_for` is a smaller modification.
 
 [float]
+[[refresh_wait_for-force-refresh]]
 === `refresh=wait_for` Can Force a Refresh
 
 If a `refresh=wait_for` request comes in when there are already

docs/reference/docs/update.asciidoc

@@ -218,6 +218,7 @@ POST test/type1/1/_update
 // TEST[continued]
 
 [float]
+[[scripted_upsert]]
 ==== `scripted_upsert`
 
 If you would like your script to run regardless of whether the document exists
@@ -244,6 +245,7 @@ POST sessions/session/dh3sgudg8gsrgl/_update
 --------------------------------------------------
 
 [float]
+[[doc_as_upsert]]
 ==== `doc_as_upsert`
 
 Instead of sending a partial `doc` plus an `upsert` doc, setting

docs/reference/getting-started.asciidoc

@@ -407,6 +407,7 @@ This REST access pattern is pervasive throughout all the API commands that if yo
 Elasticsearch provides data manipulation and search capabilities in near real time. By default, you can expect a one second delay (refresh interval) from the time you index/update/delete your data until the time that it appears in your search results. This is an important distinction from other platforms like SQL wherein data is immediately available after a transaction is completed.
 
 [float]
+[[indexing-replacing-documents]]
 === Indexing/Replacing Documents
 
 We've previously seen how we can index a single document. Let's recall that command again:

docs/reference/how-to/disk-usage.asciidoc

@@ -99,6 +99,7 @@ PUT index
 // CONSOLE
 
 [float]
+[[default-dynamic-string-mapping]]
 === Don't use default dynamic string mappings
 
 The default <<dynamic-mapping,dynamic string mappings>> will index string fields
@@ -136,6 +137,7 @@ PUT index
 // CONSOLE
 
 [float]
+[[disable-all]]
 === Disable `_all`
 
 The <<mapping-all-field,`_all`>> field indexes the value of all fields of a

docs/reference/how-to/indexing-speed.asciidoc

@@ -17,6 +17,7 @@ it is advisable to avoid going beyond a couple tens of megabytes per request
 even if larger requests seem to perform better.
 
 [float]
+[[multiple-workers-threads]]
 === Use multiple workers/threads to send data to Elasticsearch
 
 A single thread sending bulk requests is unlikely to be able to max out the

docs/reference/mapping/dynamic/templates.asciidoc

@@ -283,6 +283,7 @@ PUT my_index
 }
 --------------------------------------------------
 
+[[text-only-mappings-strings]]
 ===== `text`-only mappings for strings
 
 On the contrary to the previous example, if the only thing that you care about

docs/reference/mapping/fields/source-field.asciidoc

@@ -6,6 +6,7 @@ at index time.  The `_source` field itself is not indexed (and thus is not
 searchable), but it is stored so that it can be returned when executing
 _fetch_ requests, like <<docs-get,get>> or <<search-search,search>>.
 
+[[disable-source-field]]
 ==== Disabling the `_source` field
 
 Though very handy to have around, the source field does incur storage overhead

docs/reference/mapping/params/fielddata.asciidoc

@@ -19,6 +19,7 @@ reading the entire inverted index for each segment from disk, inverting the
 term ↔︎ document relationship, and storing the result in memory, in the JVM
 heap.
 
+[[fielddata-disabled-text-fields]]
 ==== Fielddata is disabled on `text` fields by default
 
 Fielddata can consume a *lot* of heap space, especially when loading high
@@ -77,6 +78,7 @@ PUT my_index
 <1> Use the `my_field` field for searches.
 <2> Use the `my_field.keyword` field for aggregations, sorting, or in scripts.
 
+[[enable-fielddata-text-fields]]
 ==== Enabling fielddata on `text` fields
 
 You can enable fielddata on an existing `text` field using the

docs/reference/mapping/types/geo-shape.asciidoc

@@ -249,6 +249,7 @@ API.
 --------------------------------------------------
 
 [float]
+[[linestring]]
 ===== http://geojson.org/geojson-spec.html#id3[LineString]
 
 A `linestring` defined by an array of two or more positions. By
@@ -269,6 +270,7 @@ The above `linestring` would draw a straight line starting at the White
 House to the US Capitol Building.
 
 [float]
+[[polygon]]
 ===== http://www.geojson.org/geojson-spec.html#id4[Polygon]
 
 A polygon is defined by a list of a list of points. The first and last
@@ -352,6 +354,7 @@ overriding the orientation on a document:
 --------------------------------------------------
 
 [float]
+[[multipoint]]
 ===== http://www.geojson.org/geojson-spec.html#id5[MultiPoint]
 
 A list of geojson points.
@@ -369,6 +372,7 @@ A list of geojson points.
 --------------------------------------------------
 
 [float]
+[[multilinestring]]
 ===== http://www.geojson.org/geojson-spec.html#id6[MultiLineString]
 
 A list of geojson linestrings.
@@ -388,6 +392,7 @@ A list of geojson linestrings.
 --------------------------------------------------
 
 [float]
+[[multipolygon]]
 ===== http://www.geojson.org/geojson-spec.html#id7[MultiPolygon]
 
 A list of geojson polygons.
@@ -408,6 +413,7 @@ A list of geojson polygons.
 --------------------------------------------------
 
 [float]
+[[geometry_collection]]
 ===== http://geojson.org/geojson-spec.html#geometrycollection[Geometry Collection]
 
 A collection of geojson geometry objects.

docs/reference/mapping/types/ip.asciidoc

@@ -77,6 +77,7 @@ The following parameters are accepted by `ip` fields:
     the <<mapping-source-field,`_source`>> field. Accepts `true` or `false`
     (default).
 
+[[query-ip-fields]]
 ==== Querying `ip` fields
 
 The most common way to query ip addresses is to use the

docs/reference/mapping/types/nested.asciidoc

@@ -64,6 +64,7 @@ GET my_index/_search
 // CONSOLE
 // TEST[continued]
 
+[[nested-fields-array-objects]]
 ==== Using `nested` fields for arrays of objects
 
 If you need to index arrays of objects and to maintain the independence of

docs/reference/mapping/types/percolator.asciidoc

@@ -74,6 +74,7 @@ fail.
 ==== Limitations
 
 [float]
+[[parent-child]]
 ===== Parent/child
 
 Because the `percolate` query is processing one document at a time, it doesn't support queries and filters that run

docs/reference/modules/scripting/expression.asciidoc

@@ -112,6 +112,7 @@ The following example shows the difference in years between the `date` fields da
 `doc['date1'].date.year - doc['date0'].date.year`
 
 [float]
+[[geo-point-field-api]]
 === `geo_point` field API
 [cols="<,<",options="header",]
 |=======================================================================

docs/reference/modules/snapshots.asciidoc

@@ -460,6 +460,7 @@ GET /_snapshot/my_backup/snapshot_1,snapshot_2/_status
 // CONSOLE
 
 [float]
+[[monitor-snapshot-restore-progress]]
 === Monitoring snapshot/restore progress
 
 There are several ways to monitor the progress of the snapshot and restores processes while they are running. Both

docs/reference/modules/threadpool.asciidoc

@@ -68,6 +68,7 @@ thread_pool:
 The following are the types of thread pools and their respective parameters:
 
 [float]
+[[fixed]]
 ==== `fixed`
 
 The `fixed` thread pool holds a fixed size of threads to handle the
@@ -91,6 +92,7 @@ thread_pool:
 --------------------------------------------------
 
 [float]
+[[scaling]]
 ==== `scaling`
 
 The `scaling` thread pool holds a dynamic number of threads. This

docs/reference/query-dsl/bool-query.asciidoc

@@ -75,6 +75,7 @@ POST _search
 --------------------------------------------------
 // CONSOLE
 
+[[score-bool-filter]]
 ==== Scoring with `bool.filter`
 
 Queries specified under the `filter` element have no effect on scoring --

docs/reference/query-dsl/exists-query.asciidoc

@@ -42,6 +42,7 @@ These documents would *not* match the above query:
 <3> The `user` field is missing completely.
 
 [float]
+[[null-value-mapping]]
 ==== `null_value` mapping
 
 If the field mapping includes the <<null-value,`null_value`>> setting
@@ -74,6 +75,7 @@ no values in the `user` field and thus would not match the `exists` filter:
 { "foo": "bar" }
 --------------------------------------------------
 
+[[missing-query]]
 ==== `missing` query
 
 'missing' query has been removed because it can be advantageously replaced by an `exists` query inside a must_not