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

jrodewig · jrodewig · commit 6699a5b1ddfe · 2019-04-30T10:55:10.000-04:00
diff --git a/docs/reference/aggregations/bucket/filters-aggregation.asciidoc b/docs/reference/aggregations/bucket/filters-aggregation.asciidoc
@@ -126,6 +126,7 @@ request.  The response for this example would be:
 ...
 --------------------------------------------------
 
+[[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 
diff --git a/docs/reference/aggregations/bucket/sampler-aggregation.asciidoc b/docs/reference/aggregations/bucket/sampler-aggregation.asciidoc
@@ -141,6 +141,7 @@ Please note that Elasticsearch will ignore the choice of execution hint if it is
 
 ==== 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.
diff --git a/docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc b/docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc
@@ -367,6 +367,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
diff --git a/docs/reference/aggregations/pipeline/avg-bucket-aggregation.asciidoc b/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
diff --git a/docs/reference/aggregations/pipeline/bucket-script-aggregation.asciidoc b/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>> 
diff --git a/docs/reference/aggregations/pipeline/bucket-selector-aggregation.asciidoc b/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>> 
diff --git a/docs/reference/aggregations/pipeline/cumulative-sum-aggregation.asciidoc b/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
diff --git a/docs/reference/aggregations/pipeline/derivative-aggregation.asciidoc b/docs/reference/aggregations/pipeline/derivative-aggregation.asciidoc
@@ -20,7 +20,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
diff --git a/docs/reference/aggregations/pipeline/extended-stats-bucket-aggregation.asciidoc b/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
diff --git a/docs/reference/aggregations/pipeline/max-bucket-aggregation.asciidoc b/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
diff --git a/docs/reference/aggregations/pipeline/min-bucket-aggregation.asciidoc b/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
diff --git a/docs/reference/aggregations/pipeline/percentiles-bucket-aggregation.asciidoc b/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
diff --git a/docs/reference/aggregations/pipeline/serial-diff-aggregation.asciidoc b/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 |
diff --git a/docs/reference/aggregations/pipeline/stats-bucket-aggregation.asciidoc b/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
diff --git a/docs/reference/aggregations/pipeline/sum-bucket-aggregation.asciidoc b/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
diff --git a/docs/reference/docs/update.asciidoc b/docs/reference/docs/update.asciidoc
@@ -156,6 +156,7 @@ curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
 --------------------------------------------------
 
 [float]
+[[scripted_upsert]]
 ==== `scripted_upsert`
 
 If you would like your script to run regardless of whether the document exists
@@ -181,6 +182,7 @@ curl -XPOST 'localhost:9200/sessions/session/dh3sgudg8gsrgl/_update' -d '{
 --------------------------------------------------
 
 [float]
+[[doc_as_upsert]]
 ==== `doc_as_upsert`
 
 Instead of sending a partial `doc` plus an `upsert` doc, setting
diff --git a/docs/reference/getting-started.asciidoc b/docs/reference/getting-started.asciidoc
@@ -384,6 +384,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:
diff --git a/docs/reference/mapping/fields/source-field.asciidoc b/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
diff --git a/docs/reference/mapping/params/fielddata.asciidoc b/docs/reference/mapping/params/fielddata.asciidoc
@@ -27,19 +27,6 @@ remains in memory for the lifetime of the segment.
 
 [WARNING]
 .Fielddata can fill up your heap space
-==============================================================================
-Fielddata can consume a lot of heap space, especially when loading high
-cardinality `analyzed` string fields.  Most of the time, it doesn't make sense
-to sort or aggregate on `analyzed` string fields (with the notable exception
-of the
-<<search-aggregations-bucket-significantterms-aggregation,`significant_terms`>>
-aggregation).  Always think about whether a `not_analyzed` field (which can
-use `doc_values`) would be  a better fit for your use case.
-==============================================================================
-
-TIP: The `fielddata.*` settings must have the same settings for fields of the
-same name in the same index.  Its value can be updated on existing fields
-using the <<indices-put-mapping,PUT mapping API>>.
 
 
 [[fielddata-format]]
@@ -71,9 +58,14 @@ PUT my_index
 // AUTOSENSE
 <1> The `text` field cannot be used for sorting, aggregations, or in scripts.
 
+<<<<<<< HEAD
 .Fielddata and other datatypes
 [NOTE]
 ==================================================
+=======
+[[enable-fielddata-text-fields]]
+==== Enabling fielddata on `text` fields
+>>>>>>> b7f569ec801... [DOCS] Add anchors for Asciidoctor migration (#41648)
 
 Historically, other field datatypes also used fielddata, but this has been replaced
 by index-time, disk-based <<doc-values,`doc_values`>>.
diff --git a/docs/reference/mapping/types/geo-shape.asciidoc b/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.
diff --git a/docs/reference/mapping/types/nested.asciidoc b/docs/reference/mapping/types/nested.asciidoc
@@ -63,6 +63,7 @@ GET my_index/_search
 --------------------------------------------------
 // AUTOSENSE
 
+[[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
diff --git a/docs/reference/modules/snapshots.asciidoc b/docs/reference/modules/snapshots.asciidoc
@@ -453,6 +453,7 @@ GET /_snapshot/my_backup/snapshot_1,snapshot_2/_status
 // AUTOSENSE
 
 [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
diff --git a/docs/reference/modules/threadpool.asciidoc b/docs/reference/modules/threadpool.asciidoc
@@ -78,6 +78,7 @@ NOTE: you can update thread pool settings dynamically using <<cluster-update-set
 The following are the types of thread pools and their respective parameters:
 
 [float]
+[[cached]]
 ==== `cached`
 
 The `cached` thread pool is an unbounded thread pool that will spawn a
@@ -98,6 +99,7 @@ threadpool:
 --------------------------------------------------
 
 [float]
+[[fixed]]
 ==== `fixed`
 
 The `fixed` thread pool holds a fixed size of threads to handle the
@@ -121,6 +123,7 @@ threadpool:
 --------------------------------------------------
 
 [float]
+[[scaling]]
 ==== `scaling`
 
 The `scaling` thread pool holds a dynamic number of threads. This number is
diff --git a/docs/reference/query-dsl/bool-query.asciidoc b/docs/reference/query-dsl/bool-query.asciidoc
@@ -71,6 +71,7 @@ final `_score` for each document.
 }
 --------------------------------------------------
 
+[[score-bool-filter]]
 ==== Scoring with `bool.filter` 
 
 Queries specified under the `filter` element have no effect on scoring --
diff --git a/docs/reference/query-dsl/exists-query.asciidoc b/docs/reference/query-dsl/exists-query.asciidoc
@@ -38,6 +38,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
@@ -70,6 +71,7 @@ no values in the `user` field and thus would not match the `exists` filter:
 { "foo": "bar" }
 --------------------------------------------------
 
+[[missing-query]]
 ==== `missing` query
 
 The exists query can advantageously replace the `missing` query when used inside a must_not clause as follows:
diff --git a/docs/reference/query-dsl/has-child-query.asciidoc b/docs/reference/query-dsl/has-child-query.asciidoc
@@ -46,6 +46,7 @@ inside the `has_child` query:
 --------------------------------------------------
 
 [float]
+[[min-max-children]]
 ==== Min/Max Children
 
 The `has_child` query allows you to specify that a minimum and/or maximum
diff --git a/docs/reference/query-dsl/multi-match-query.asciidoc b/docs/reference/query-dsl/multi-match-query.asciidoc
@@ -17,6 +17,7 @@ to allow multi-field queries:
 <2> The fields to be queried.
 
 [float]
+[[field-boost]]
 ==== `fields` and per-field boosting
 
 Fields can be specified with wildcards, eg:
@@ -324,6 +325,7 @@ Also, accepts `analyzer`, `boost`, `operator`, `minimum_should_match`,
 `zero_terms_query` and `cutoff_frequency`, as explained in
 <<query-dsl-match-query, match query>>.
 
+[[cross-field-analysis]]
 ===== `cross_field` and analysis
 
 The `cross_field` type can only work in term-centric mode on fields that have
@@ -418,6 +420,7 @@ which will be executed as:
     blended("will",  fields: [first, first.edge, last.edge, last])
     blended("smith", fields: [first, first.edge, last.edge, last])
 
+[[tie-breaker]]
 ===== `tie_breaker`
 
 By default, each per-term `blended` query will use the best score returned by

Original file line number	Diff line number	Diff line change
@@ -20,7 +20,9 @@ A `cumulative_sum` aggregation looks like this in isolation:
`20`	`20`	`}`
`21`	`21`	`--------------------------------------------------`
`22`	`22`
	`23`	`+[[cumulative-sum-params]]`
`23`	`24`	.`cumulative_sum` Parameters
	`25`	`+[options="header"]`
`24`	`26`	`\|===`
`25`	`27`	`\|Parameter Name \|Description \|Required \|Default Value`
`26`	`28`	\|`buckets_path` \|The path to the buckets we wish to find the cumulative sum for (see <<buckets-path-syntax>> for more
Original file line number	Diff line number	Diff line change
@@ -20,7 +20,9 @@ A `derivative` aggregation looks like this in isolation:
`20`	`20`	`}`
`21`	`21`	`--------------------------------------------------`
`22`	`22`
	`23`	`+[[derivative-params]]`
`23`	`24`	.`derivative` Parameters
	`25`	`+[options="header"]`
`24`	`26`	`\|===`
`25`	`27`	`\|Parameter Name \|Description \|Required \|Default Value`
`26`	`28`	\|`buckets_path` \|The path to the buckets we wish to find the derivative for (see <<buckets-path-syntax>> for more
Original file line number	Diff line number	Diff line change
@@ -21,7 +21,9 @@ A `extended_stats_bucket` aggregation looks like this in isolation:
`21`	`21`	`}`
`22`	`22`	`--------------------------------------------------`
`23`	`23`
	`24`	`+[[extended-stats-bucket-params]]`
`24`	`25`	.`extended_stats_bucket` Parameters
	`26`	`+[options="header"]`
`25`	`27`	`\|===`
`26`	`28`	`\|Parameter Name \|Description \|Required \|Default Value`
`27`	`29`	\|`buckets_path` \|The path to the buckets we wish to calculate stats for (see <<buckets-path-syntax>> for more
Original file line number	Diff line number	Diff line change
@@ -20,7 +20,9 @@ A `max_bucket` aggregation looks like this in isolation:
`20`	`20`	`}`
`21`	`21`	`--------------------------------------------------`
`22`	`22`
	`23`	`+[[max-bucket-params]]`
`23`	`24`	.`max_bucket` Parameters
	`25`	`+[options="header"]`
`24`	`26`	`\|===`
`25`	`27`	`\|Parameter Name \|Description \|Required \|Default Value`
`26`	`28`	\|`buckets_path` \|The path to the buckets we wish to find the maximum for (see <<buckets-path-syntax>> for more