snapshots.asciidoc 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586
  1. [discrete]
  2. [[breaking_80_snapshots_changes]]
  3. ==== Snapshot and restore 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. .The `repositories.fs.compress` node-level setting has been removed.
  8. [%collapsible]
  9. ====
  10. *Details* +
  11. For shared file system repositories (`"type": "fs"`), the node level setting `repositories.fs.compress` could
  12. previously be used to enable compression for all shared file system repositories where `compress` was not specified.
  13. The `repositories.fs.compress` setting has been removed.
  14. *Impact* +
  15. Use the repository specific `compress` setting to enable compression. See
  16. {ref}/snapshots-register-repository.html[Register a snapshot repository] for
  17. information on the `compress` setting.
  18. Discontinue use of the `repositories.fs.compress` node-level setting.
  19. ====
  20. .Metadata files are now compressed by default.
  21. [%collapsible]
  22. ====
  23. *Details* +
  24. Previously, the default value for `compress` was `false`. The default has been changed to `true`.
  25. This change will affect both newly created repositories and existing repositories where `compress=false` has not been
  26. explicitly specified.
  27. For more information on the compress option, see
  28. {ref}/snapshots-register-repository.html[Register a snapshot repository].
  29. *Impact* +
  30. Update your workflow and applications to assume a default value of `true` for
  31. the `compress` parameter.
  32. ====
  33. .The S3 repository plugin now uses a DNS-style access pattern by default.
  34. [%collapsible]
  35. ====
  36. *Details* +
  37. Starting in version 7.4 the `repository-s3` plugin does not use the
  38. now-deprecated path-style access pattern by default. In versions 7.0, 7.1, 7.2
  39. and 7.3 the `repository-s3` plugin always used the path-style access pattern.
  40. This is a breaking change for deployments that only support path-style access
  41. but which are recognized as supporting DNS-style access by the AWS SDK. This
  42. breaking change was made necessary by
  43. https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/[AWS's
  44. announcement] that the path-style access pattern is deprecated and will be
  45. unsupported on buckets created after September 30th 2020.
  46. *Impact* +
  47. If your deployment only supports path-style access and is affected by this
  48. change then you must configure the S3 client setting `path_style_access` to
  49. `true`.
  50. ====
  51. .Restore requests no longer accept settings.
  52. [%collapsible]
  53. ====
  54. *Details* +
  55. In earlier versions, you could pass both `settings` and `index_settings` in the
  56. body of a restore snapshot request, but the `settings` value was ignored. The
  57. restore snapshot API now rejects requests that include a `settings` value.
  58. *Impact* +
  59. Discontinue use of the `settings` parameter in restore
  60. snapshot request. Requests that include these parameters will return an error.
  61. ====
  62. .The repository stats API has been removed.
  63. [%collapsible]
  64. ====
  65. *Details* +
  66. The repository stats API has been removed. We deprecated this experimental API
  67. in 7.10.0.
  68. *Impact* +
  69. Use the {ref}/repositories-metering-apis.html[repositories metering APIs]
  70. instead.
  71. ====
  72. // end::notable-breaking-changes[]