index-setting-changes.asciidoc 2.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374
  1. [discrete]
  2. [[breaking_80_index_setting_changes]]
  3. ==== Index setting 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. [[index-max-adjacency-matrix-filters-removed]]
  8. .The `index.max_adjacency_matrix_filters` index setting has been removed.
  9. [%collapsible]
  10. ====
  11. *Details* +
  12. The `index.max_adjacency_matrix_filters` index setting has been removed.
  13. Previously, you could use this setting to configure the maximum number of
  14. filters for the
  15. {ref}/search-aggregations-bucket-adjacency-matrix-aggregation.html[adjacency
  16. matrix aggregation]. The `indices.query.bool.max_clause_count` index setting now
  17. determines the maximum number of filters for the aggregation.
  18. *Impact* +
  19. Discontinue use of the `index.max_adjacency_matrix_filters` index setting.
  20. Requests that include the index setting will return an error. If you upgrade a
  21. cluster with a 7.x index that already contains the setting, {es} will
  22. {ref}/archived-settings.html#archived-index-settings[archive the setting].
  23. Remove the index setting from index and component templates. Attempts to use a
  24. template that contains the setting will fail and return an error. This includes
  25. automated operations, such the {ilm-init} rollover action.
  26. ====
  27. .The `index.force_memory_term_dictionary` setting has been removed.
  28. [%collapsible]
  29. ====
  30. *Details* +
  31. The `index.force_memory_term_dictionary` setting was introduced in 7.0 as a
  32. temporary measure to allow users to opt-out of the optimization that leaves the
  33. term dictionary on disk when appropriate. This optimization is now mandatory
  34. and the setting is removed.
  35. *Impact* +
  36. Discontinue use of the `index.force_memory_term_dictionary` index setting.
  37. Requests that include this setting will return an error.
  38. ====
  39. .The `index.soft_deletes.enabled` setting has been removed.
  40. [%collapsible]
  41. ====
  42. *Details* +
  43. Creating indices with soft deletes disabled was deprecated in 7.6 and
  44. is no longer supported in 8.0. The `index.soft_deletes.enabled` setting
  45. can no longer be set to `false`.
  46. *Impact* +
  47. Discontinue use of the `index.soft_deletes.enabled` index setting. Requests that
  48. set `index.soft_deletes.enabled` to `false` will return an error.
  49. ====
  50. .The `index.translog.retention.age` and `index.translog.retention.size` settings have been removed.
  51. [%collapsible]
  52. ====
  53. *Details* +
  54. Translog retention settings `index.translog.retention.age` and
  55. `index.translog.retention.size` were effectively ignored in 7.4, deprecated in
  56. 7.7, and removed in 8.0 in favor of
  57. {ref}/index-modules-history-retention.html[soft deletes].
  58. *Impact* +
  59. Discontinue use of the `index.translog.retention.age` and
  60. `index.translog.retention.size` index settings. Requests that
  61. include these settings will return an error.
  62. ====
  63. //end::notable-breaking-changes[]