Update Documentation Feature Flags [1.4.0.Beta1]

Author: s1monw

docs/reference/analysis/tokenfilters/keep-types-tokenfilter.asciidoc

@@ -1,7 +1,7 @@
 [[analysis-keep-types-tokenfilter]]
 === Keep Types Token Filter
 
-coming[1.4.0.Beta1]
+added[1.4.0.Beta1]
 
 A token filter of type `keep_types` that only keeps tokens with a token type 
 contained in a predefined set.

docs/reference/api-conventions.asciidoc

@@ -51,7 +51,7 @@ specified to expand to all indices.
 +
 If `none` is specified then wildcard expansion will be disabled and if `all` 
 is specified, wildcard expressions will expand to all indices (this is equivalent 
-to specifying `open,closed`). coming[1.4.0.Beta1]
+to specifying `open,closed`). added[1.4.0.Beta1]
 
 The defaults settings for the above parameters depend on the api being used.
 

docs/reference/docs/get.asciidoc

@@ -125,7 +125,7 @@ will fail.
 [float]
 [[generated-fields]]
 === Generated fields
-coming[1.4.0.Beta1]
+added[1.4.0.Beta1]
 
 If no refresh occurred between indexing and refresh, GET will access the transaction log to fetch the document. However, some fields are generated only when indexing. 
 If you try to access a field that is only generated when indexing, you will get an exception (default). You can choose to ignore field that are generated if the transaction log is accessed by setting `ignore_errors_on_generated_fields=true`.

docs/reference/docs/multi-get.asciidoc

@@ -181,7 +181,7 @@ curl 'localhost:9200/_mget' -d '{
 [float]
 === Generated fields
 
-coming[1.4.0.Beta1]
+added[1.4.0.Beta1]
 
 See <<generated-fields>> for fields are generated only when indexing. 
 

docs/reference/docs/multi-termvectors.asciidoc

@@ -3,7 +3,7 @@
 
 Multi termvectors API allows to get multiple termvectors at once. The
 documents from which to retrieve the term vectors are specified by an index,
-type and id. But the documents could also be artificially provided coming[1.4.0.Beta1].
+type and id. But the documents could also be artificially provided added[1.4.0.Beta1].
 The response includes a `docs`
 array with all the fetched termvectors, each element having the structure
 provided by the <<docs-termvectors,termvectors>>
@@ -92,7 +92,7 @@ curl 'localhost:9200/testidx/test/_mtermvectors' -d '{
 }'
 --------------------------------------------------
 
-Additionally coming[1.4.0.Beta1], just like for the <<docs-termvectors,termvectors>>
+Additionally added[1.4.0.Beta1], just like for the <<docs-termvectors,termvectors>>
 API, term vectors could be generated for user provided documents. The syntax
 is similar to the <<search-percolate,percolator>> API. The mapping used is
 determined by `_index` and `_type`.

docs/reference/docs/termvectors.asciidoc

@@ -3,7 +3,7 @@
 
 Returns information and statistics on terms in the fields of a particular
 document. The document could be stored in the index or artificially provided
-by the user coming[1.4.0.Beta1]. Note that for documents stored in the index, this
+by the user added[1.4.0.Beta1]. Note that for documents stored in the index, this
 is a near realtime API as the term vectors are not available until the next
 refresh.
 
@@ -22,7 +22,7 @@ curl -XGET 'http://localhost:9200/twitter/tweet/1/_termvector?fields=text,...'
 
 or by adding the requested fields in the request body (see
 example below). Fields can also be specified with wildcards
-in similar way to the <<query-dsl-multi-match-query,multi match query>> coming[1.4.0.Beta1].
+in similar way to the <<query-dsl-multi-match-query,multi match query>> added[1.4.0.Beta1].
 
 [float]
 === Return values
@@ -43,7 +43,7 @@ If the requested information wasn't stored in the index, it will be
 computed on the fly if possible. Additionally, term vectors could be computed
 for documents not even existing in the index, but instead provided by the user.
 
-coming[1.4.0.Beta1,The ability to computed term vectors on the fly as well as support for artificial documents is only available from 1.4.0 onwards (see below example 2 and 3 respectively)]
+added[1.4.0.Beta1,The ability to computed term vectors on the fly as well as support for artificial documents is only available from 1.4.0 onwards (see below example 2 and 3 respectively)]
 
 [WARNING]
 ======
@@ -230,7 +230,7 @@ Response:
 --------------------------------------------------
 
 [float]
-=== Example 2 coming[1.4.0.Beta1]
+=== Example 2 added[1.4.0.Beta1]
 
 Term vectors which are not explicitly stored in the index are automatically
 computed on the fly. The following request returns all information and statistics for the
@@ -249,7 +249,7 @@ curl -XGET 'http://localhost:9200/twitter/tweet/1/_termvector?pretty=true' -d '{
 --------------------------------------------------
 
 [float]
-=== Example 3 coming[1.4.0.Beta1]
+=== Example 3 added[1.4.0.Beta1]
 
 Additionally, term vectors can also be generated for artificial documents,
 that is for documents not present in the index. The syntax is similar to the

docs/reference/docs/update.asciidoc

@@ -145,7 +145,7 @@ curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
  }
 }'
 --------------------------------------------------
-coming[1.4.0.Beta1]
+added[1.4.0.Beta1]
 
 If the document does not exist you may want your update script to
 run anyway in order to initialize the document contents using 

docs/reference/index-modules/fielddata.asciidoc

@@ -28,7 +28,7 @@ example, can be set to `5m` for a 5 minute expiry.
 [[circuit-breaker]]
 === Circuit Breaker
 
-coming[1.4.0.Beta1,Prior to 1.4.0 there was only a single circuit breaker for fielddata]
+added[1.4.0.Beta1,Prior to 1.4.0 there was only a single circuit breaker for fielddata]
 
 Elasticsearch contains multiple circuit breakers used to prevent operations from
 causing an OutOfMemoryError. Each breaker specifies a limit for how much memory
@@ -69,7 +69,7 @@ parameters:
 [[request-circuit-breaker]]
 ==== Request circuit breaker
 
-coming[1.4.0.Beta1]
+added[1.4.0.Beta1]
 
 The request circuit breaker allows Elasticsearch to prevent per-request data
 structures (for example, memory used for calculating aggregations during a

docs/reference/index-modules/query-cache.asciidoc

@@ -1,7 +1,7 @@
 [[index-modules-shard-query-cache]]
 == Shard query cache
 
-coming[1.4.0.Beta1]
+added[1.4.0.Beta1]
 
 When a search request is run against an index or against many indices, each
 involved shard executes the search locally and returns its local results to

docs/reference/indices/aliases.asciidoc

@@ -74,7 +74,7 @@ the same index. The filter can be defined using Query DSL and is applied
 to all Search, Count, Delete By Query and More Like This operations with
 this alias.
 
-coming[1.4.0.Beta1,Fields referred to in alias filters must exist in the mappings of the index/indices pointed to by the alias]
+added[1.4.0.Beta1,Fields referred to in alias filters must exist in the mappings of the index/indices pointed to by the alias]
 
 To create a filtered alias, first we need to ensure that the fields already
 exist in the mapping:
@@ -312,7 +312,7 @@ Possible options:
 
 The rest endpoint is: `/{index}/_alias/{alias}`.
 
-coming[1.4.0.Beta1,The API will always include an `aliases` section, even if there aren't any aliases. Previous versions would not return the `aliases` section]
+added[1.4.0.Beta1,The API will always include an `aliases` section, even if there aren't any aliases. Previous versions would not return the `aliases` section]
 
 WARNING: For future versions of Elasticsearch, the default <<multi-index>> options will error if a requested index is unavailable. This is to bring 
 this API in line with the other indices GET APIs