mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-09 14:34:43 +00:00
Docs: Updated version annotations in master
This commit is contained in:
Clinton Gormley
parent
88ee7a5dca
commit
abc7de96ae
@ -22,8 +22,6 @@ $ curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'
|
||||
}
|
||||
--------------------------------------------------
|
||||
|
||||
coming[1.5.0, number of pending tasks was added in 1.5.0]
|
||||
|
||||
The API can also be executed against one or more indices to get just the
|
||||
specified indices health:
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
[[elasticsearch-reference]]
|
||||
= Reference
|
||||
|
||||
:version: 1.5.0
|
||||
:version: 1.5.1
|
||||
:branch: 1.5
|
||||
:jdk: 1.8.0_25
|
||||
:defguide: https://www.elastic.co/guide/en/elasticsearch/guide/current
|
||||
|
||||
@ -19,7 +19,6 @@ curl -XGET http://localhost:9200/_recovery?pretty&human
|
||||
--------------------------------------------------
|
||||
|
||||
Response:
|
||||
coming[1.5.0, this syntax was change to fix inconsistencies with other API]
|
||||
[source,js]
|
||||
--------------------------------------------------
|
||||
{
|
||||
@ -94,7 +93,6 @@ In some cases a higher level of detail may be preferable. Setting "detailed=true
|
||||
curl -XGET http://localhost:9200/_recovery?pretty&human&detailed=true
|
||||
--------------------------------------------------
|
||||
|
||||
coming[1.5.0, this syntax was change to fix inconsistencies with other API]
|
||||
Response:
|
||||
|
||||
[source,js]
|
||||
|
||||
@ -122,8 +122,6 @@ You can also set the default value to any date respecting <<mapping-timestamp-fi
|
||||
|
||||
If you don't provide any timestamp value, _timestamp will be set to this default value.
|
||||
|
||||
coming[1.5.0]
|
||||
|
||||
In elasticsearch 1.4, we allowed setting explicitly `"default":null` which is not possible anymore
|
||||
as we added a new `ignore_missing` setting.
|
||||
When reading an index created with elasticsearch 1.4 and using this, we automatically update it by
|
||||
|
||||
@ -378,7 +378,7 @@ that can be used for configuring this sandbox:
|
||||
|
||||
`script.groovy.sandbox.enabled`::
|
||||
|
||||
Flag to enable the sandbox (defaults to `false` added[v1.4.3] meaning the sandbox is
|
||||
Flag to enable the sandbox (defaults to `false` meaning the sandbox is
|
||||
disabled).
|
||||
|
||||
When specifying whitelist or blacklist settings for the groovy sandbox, all
|
||||
|
||||
@ -85,7 +85,6 @@ the JVM. It is automatically enabled when using
|
||||
`NodeBuilder#local(true)`.
|
||||
|
||||
[float]
|
||||
coming[1.5.0]
|
||||
=== Transport Tracer
|
||||
|
||||
The transport module has a dedicated tracer logger which, when activated, logs incoming and out going requests. The log can be dynamically activated
|
||||
|
||||
@ -86,8 +86,6 @@ query. The parameter `boost_mode` defines how:
|
||||
`max`:: max of query score and function score
|
||||
`min`:: min of query score and function score
|
||||
|
||||
coming[1.5.0]
|
||||
|
||||
By default, modifying the score does not change which documents match. To exclude
|
||||
documents that do not meet a certain score threshold the `min_score` parameter can be set to the desired score threshold.
|
||||
|
||||
|
||||
@ -347,8 +347,6 @@ It is hard to say which one of the different heuristics will be the best choice
|
||||
If none of the above measures suits your usecase than another option is to implement a custom significance measure:
|
||||
|
||||
===== scripted
|
||||
coming[1.5.0]
|
||||
|
||||
Customized scores can be implemented via a script:
|
||||
|
||||
[source,js]
|
||||
|
||||
@ -46,8 +46,6 @@ The above aggregation computes the grades statistics over all documents. The agg
|
||||
The name of the aggregation (`grades_stats` above) also serves as the key by which the aggregation result can be retrieved from the returned response.
|
||||
|
||||
==== Standard Deviation Bounds
|
||||
added[1.4.3]
|
||||
|
||||
By default, the `extended_stats` metric will return an object called `std_deviation_bounds`, which provides an interval of plus/minus two standard
|
||||
deviations from the mean. This can be a useful way to visualize variance of your data. If you want a different boundary, for example
|
||||
three standard deviations, you can set `sigma` in the request:
|
||||
@ -65,7 +63,7 @@ three standard deviations, you can set `sigma` in the request:
|
||||
}
|
||||
}
|
||||
--------------------------------------------------
|
||||
<1> `sigma` controls how many standard deviations +/- from the mean should be displayed added[1.4.3]
|
||||
<1> `sigma` controls how many standard deviations +/- from the mean should be displayed
|
||||
|
||||
`sigma` can be any non-negative double, meaning you can request non-integer values such as `1.5`. A value of `0` is valid, but will simply
|
||||
return the average for both `upper` and `lower` bounds.
|
||||
|
||||
@ -28,7 +28,7 @@ documentation of the mustache project].
|
||||
NOTE: The mustache language is implemented in elasticsearch as a sandboxed
|
||||
scripting language, hence it obeys settings that may be used to enable or
|
||||
disable scripts per language, source and operation as described in
|
||||
<<enable-dynamic-scripting, scripting docs>> coming[1.6.0, `mustache` scripts were always on before and it wasn't possible to disable them].
|
||||
<<enable-dynamic-scripting, scripting docs>>
|
||||
|
||||
[float]
|
||||
==== More template examples
|
||||
|
||||
@ -323,6 +323,6 @@ appender section contains the destinations for the logs. Extensive information
|
||||
on how to customize logging and all the supported appenders can be found on
|
||||
the http://logging.apache.org/log4j/1.2/manual.html[log4j documentation].
|
||||
|
||||
coming[1.5.0] Additional Appenders and other logging classes provided by
|
||||
Additional Appenders and other logging classes provided by
|
||||
http://logging.apache.org/log4j/extras/[log4j-extras] are also available,
|
||||
out of the box.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user