rest.asciidoc 2.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. [[breaking_50_rest_api_changes]]
  2. === REST API changes
  3. ==== id values longer than 512 bytes are rejected
  4. When specifying an `_id` value longer than 512 bytes, the request will be
  5. rejected.
  6. ==== `/_optimize` endpoint removed
  7. The deprecated `/_optimize` endpoint has been removed. The `/_forcemerge`
  8. endpoint should be used in lieu of optimize.
  9. The `GET` HTTP verb for `/_forcemerge` is no longer supported, please use the
  10. `POST` HTTP verb.
  11. ==== Removed `mem` section from `/_cluster/stats` response
  12. The `mem` section contained only one value, the total memory available
  13. throughout all nodes in the cluster. The section was removed as it didn't
  14. prove useful.
  15. ==== Revised node roles aggregate returned by `/_cluster/stats`
  16. The `client`, `master_only`, `data_only` and `master_data` fields have been
  17. removed in favor of `master`, `data`, `ingest` and `coordinating_only`. A
  18. node can contribute to multiple counts as it can have multiple roles. Every
  19. node is implicitly a coordinating node, so whenever a node has no explicit
  20. roles, it will be counted as coordinating only.
  21. ==== Removed shard `version` information from `/_cluster/state` routing table
  22. We now store allocation id's of shards in the cluster state and use that to
  23. select primary shards instead of the version information.
  24. ==== Node roles are not part of node attributes anymore
  25. Node roles are now returned in a specific section, called `roles`, as part of
  26. nodes stats and nodes info response. The new section is an array that holds all
  27. the different roles that each node fulfills. In case the array is returned
  28. empty, that means that the node is a coordinating only node.
  29. ==== Forbid unquoted JSON
  30. Previously, JSON documents were allowed with unquoted field names, which isn't
  31. strictly JSON and broke some Elasticsearch clients. If documents were already
  32. indexed with unquoted fields in a previous vesrion of Elasticsearch, some
  33. operations may throw errors. To accompany this, a commented out JVM option has
  34. been added to the `jvm.options` file:
  35. `-Delasticsearch.json.allow_unquoted_field_names`.
  36. Note that this option is provided solely for migration purposes and will be
  37. removed in Elasticsearch 6.0.0.
  38. ==== Analyze API changes
  39. The deprecated `filters`/`token_filters`/`char_filters` parameter has been
  40. renamed `filter`/`token_filter`/`char_filter`.
  41. ==== `DELETE /_query` endpoint removed
  42. The `DELETE /_query` endpoint provided by the Delete-By-Query plugin has been
  43. removed and replaced by the <<docs-delete-by-query,Delete By Query API>>.