mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-25 17:38:44 +00:00
Update Documentation Feature Flags [1.1.0]
This commit is contained in:
bleskes
Boaz Leskes
parent
424bffca74
commit
5d832374dd
@ -20,7 +20,7 @@ equivalents, if one exists. Example:
|
||||
}
|
||||
--------------------------------------------------
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
Accepts `preserve_original` setting which defaults to false but if true
|
||||
will keep the oringal token as well as emit the folded token. For
|
||||
example:
|
||||
|
||||
@ -146,7 +146,7 @@ All the disable allocation settings have been deprecated in favour for
|
||||
`discovery.zen.minimum_master_nodes`::
|
||||
See <<modules-discovery-zen>>
|
||||
|
||||
`discovery.zen.publish_timeout` coming[1.1.0, The setting existed before but wasn't dynamic]::
|
||||
`discovery.zen.publish_timeout` added[1.1.0, The setting existed before but wasn't dynamic]::
|
||||
See <<modules-discovery-zen>>
|
||||
|
||||
[float]
|
||||
|
||||
@ -198,7 +198,7 @@ curl -XPUT 'localhost:9200/users/_alias/user_12' -d '{
|
||||
[[alias-index-creation]]
|
||||
=== Aliases during index creation
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
Aliases can also be specified during <<create-index-aliases,index creation>>:
|
||||
|
||||
|
||||
@ -109,7 +109,7 @@ curl -XPUT localhost:9200/test -d '{
|
||||
[[create-index-aliases]]
|
||||
=== Aliases
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
The create index API allows also to provide a set of <<indices-aliases,aliases>>:
|
||||
|
||||
|
||||
@ -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`.
|
||||
|
||||
`force`:: Force a merge operation, even if there is a single segment in the
|
||||
shard with no deletions. coming[1.1.0]
|
||||
shard with no deletions. added[1.1.0]
|
||||
|
||||
[float]
|
||||
[[optimize-multi-index]]
|
||||
|
||||
@ -27,7 +27,7 @@ Defines a template named template_1, with a template pattern of `te*`.
|
||||
The settings and mappings will be applied to any index name that matches
|
||||
the `te*` template.
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
It is also possible to include aliases in an index template as follows:
|
||||
|
||||
|
||||
@ -158,5 +158,5 @@ updates its own cluster state and replies to the master node, which waits for
|
||||
all nodes to respond, up to a timeout, before going ahead processing the next
|
||||
updates in the queue. The `discovery.zen.publish_timeout` is set by default
|
||||
to 30 seconds and can be changed dynamically through the
|
||||
<<cluster-update-settings,cluster update settings api>> coming[1.1.0, The
|
||||
<<cluster-update-settings,cluster update settings api>> added[1.1.0, The
|
||||
setting existed before but wasn't dynamic].
|
||||
|
||||
@ -58,7 +58,7 @@ in a `dis_max` query. By setting `use_dis_max` to `false`, they will be wrapped
|
||||
[float]
|
||||
=== Types of `multi_match` query:
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
The way the `multi_match` query is executed internally depends on the `type`
|
||||
parameter, which can be set to:
|
||||
|
||||
@ -72,7 +72,7 @@ both>>.
|
||||
|`lenient` |If set to `true` will cause format based failures (like
|
||||
providing text to a numeric field) to be ignored.
|
||||
|
||||
|`locale` | coming[1.1.0] Locale that should be used for string conversions.
|
||||
|`locale` | added[1.1.0] Locale that should be used for string conversions.
|
||||
Defaults to `ROOT`.
|
||||
|=======================================================================
|
||||
|
||||
|
||||
@ -44,7 +44,7 @@ enable. Defaults to `ALL`.
|
||||
be automatically lower-cased or not (since they are not analyzed). Defaults to
|
||||
true.
|
||||
|
||||
|`locale` | coming[1.1.0] Locale that should be used for string conversions.
|
||||
|`locale` | added[1.1.0] Locale that should be used for string conversions.
|
||||
Defaults to `ROOT`.
|
||||
|=======================================================================
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
[[query-dsl-template-query]]
|
||||
=== Template Query
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
A query that accepts a query template and a map of key/value pairs to fill in
|
||||
template parameters.
|
||||
|
||||
@ -10,7 +10,7 @@ This feature is marked as experimental, and may be subject to change in the
|
||||
future. If you use this feature, please let us know your experience with it!
|
||||
=====
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
|
||||
.Example use cases:
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
[[search-aggregations-metrics-cardinality-aggregation]]
|
||||
=== Cardinality
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
A `single-value` metrics aggregation that calculates an approximate count of
|
||||
distinct values. Values can be extracted either from specific fields in the
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
[[search-aggregations-metrics-percentile-aggregation]]
|
||||
=== Percentiles
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
A `multi-value` metrics aggregation that calculates one or more percentiles
|
||||
over numeric values extracted from the aggregated documents. These values
|
||||
|
||||
@ -82,7 +82,7 @@ for <<query-dsl-function-score-query,`function query`>> rescores.
|
||||
|
||||
==== Multiple Rescores
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
It is also possible to execute multiple rescores in sequence:
|
||||
[source,js]
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
[[search-template]]
|
||||
== Search Template
|
||||
|
||||
coming[1.1.0]
|
||||
added[1.1.0]
|
||||
|
||||
The `/_search/template` endpoint allows to use the mustache language to pre render search requests,
|
||||
before they are executed and fill existing templates with template parameters.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user