honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-09 14:34:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update migrate_2_0.asciidoc

Browse Source 
Fixed bad heading levels in breaking changes
This commit is contained in:
Clinton Gormley 2015-02-25 14:10:17 +01:00
parent 0c61ea803d
commit 5146cf6256
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/migration/migrate_2_0.asciidoc
View File

@ -109,7 +109,7 @@ Some query builders have been removed or renamed:
* `filtered(...)` removed. Use `filteredQuery(...)` instead. * `filtered(...)` removed. Use `filteredQuery(...)` instead.
* `inQuery(...)` removed. * `inQuery(...)` removed.
==== Aggregations === Aggregations
The `date_histogram` aggregation now returns a `Histogram` object in the response, and the `DateHistogram` class has been removed. Similarly The `date_histogram` aggregation now returns a `Histogram` object in the response, and the `DateHistogram` class has been removed. Similarly
the `date_range`, `ipv4_range`, and `geo_distance` aggregations all return a `Range` object in the response, and the `IPV4Range`, `DateRange`, the `date_range`, `ipv4_range`, and `geo_distance` aggregations all return a `Range` object in the response, and the `IPV4Range`, `DateRange`,
@ -146,7 +146,7 @@ The `parent` parameter has been removed from the update request. Before 2.x it j
`routing` setting should be used instead. The `parent` setting was confusing, because it had the impression that the parent `routing` setting should be used instead. The `parent` setting was confusing, because it had the impression that the parent
a child documents points to can be changed but this is not true. a child documents points to can be changed but this is not true.
==== Delete by query === Delete by query
The meaning of the `_shards` headers in the delete by query response has changed. Before version 2.0 the `total`, The meaning of the `_shards` headers in the delete by query response has changed. Before version 2.0 the `total`,
`successful` and `failed` fields in the header are based on the number of primary shards. The failures on replica `successful` and `failed` fields in the header are based on the number of primary shards. The failures on replica