indices.asciidoc 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  1. [float]
  2. [[breaking_80_indices_changes]]
  3. === Indices changes
  4. //NOTE: The notable-breaking-changes tagged regions are re-used in the
  5. //Installation and Upgrade Guide
  6. //tag::notable-breaking-changes[]
  7. //end::notable-breaking-changes[]
  8. .The force merge API's `max_num_segments` and `only_expunge_deletes` parameters cannot both be specified in the same request.
  9. [%collapsible]
  10. ====
  11. *Details* +
  12. Previously, the force merge API allowed the parameters `only_expunge_deletes`
  13. and `max_num_segments` to be set to a non default value at the same time. But
  14. the `max_num_segments` was silently ignored when `only_expunge_deletes` is set
  15. to `true`, leaving the false impression that it has been applied.
  16. *Impact* +
  17. When using the {ref}/indices-forcemerge.html[force merge API], do not specify
  18. values for both the `max_num_segments` and `only_expunge_deletes` parameters.
  19. Requests that include values for both parameters will return an error.
  20. ====
  21. .The `index.force_memory_term_dictionary` setting has been removed.
  22. [%collapsible]
  23. ====
  24. *Details* +
  25. The `index.force_memory_term_dictionary` setting was introduced in 7.0 as a
  26. temporary measure to allow users to opt-out of the optimization that leaves the
  27. term dictionary on disk when appropriate. This optimization is now mandatory
  28. and the setting is removed.
  29. *Impact* +
  30. Discontinue use of the `index.force_memory_term_dictionary` index setting.
  31. Requests that include this setting will return an error.
  32. ====
  33. .The put index template API's `template` parameter has been removed.
  34. [%collapsible]
  35. ====
  36. *Details* +
  37. In 6.0, we deprecated the `template` parameter in put index template requests
  38. in favor of using `index_patterns`. Support for the `template` parameter is now
  39. removed in 8.0.
  40. *Impact* +
  41. Use the {ref}/indices-templates-v1.html[put index template API]'s
  42. `index_patterns` parameter. Requests that include the `template` parameter will
  43. return an error.
  44. ====
  45. .Synced flush has been removed.
  46. [%collapsible]
  47. ====
  48. *Details* +
  49. Synced flush was deprecated in 7.6 and is removed in 8.0. Use a regular flush
  50. instead as it has the same effect as a synced flush in 7.6 and later.
  51. *Impact* +
  52. Use the {ref}/indices-flush.html[flush API]. Requests to the
  53. `/<index>/flush/synced` or `/flush/synced` endpoints will return an error.
  54. ====
  55. .The `index.soft_deletes.enabled` setting has been removed.
  56. [%collapsible]
  57. ====
  58. *Details* +
  59. Creating indices with soft deletes disabled was deprecated in 7.6 and
  60. is no longer supported in 8.0. The `index.soft_deletes.enabled` setting
  61. can no longer be set to `false`.
  62. *Impact* +
  63. Discontinue use of the `index.soft_deletes.enabled` index setting. Requests that
  64. set `index.soft_deletes.enabled` to `false` will return an error.
  65. ====
  66. .The `index.translog.retention.age` and `index.translog.retention.size` settings have been removed.
  67. [%collapsible]
  68. ====
  69. *Details* +
  70. Translog retention settings `index.translog.retention.age` and
  71. `index.translog.retention.size` were effectively ignored in 7.4, deprecated in
  72. 7.7, and removed in 8.0 in favor of
  73. {ref}/index-modules-history-retention.html[soft deletes].
  74. *Impact* +
  75. Discontinue use of the `index.translog.retention.age` and
  76. `index.translog.retention.size` index settings. Requests that
  77. include these settings will return an error.
  78. ====