migrate_8_7.asciidoc 1.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. [[migrating-8.7]]
  2. == Migrating to 8.7
  3. ++++
  4. <titleabbrev>8.7</titleabbrev>
  5. ++++
  6. This section discusses the changes that you need to be aware of when migrating
  7. your application to {es} 8.7.
  8. See also <<release-highlights>> and <<es-release-notes>>.
  9. [discrete]
  10. [[breaking-changes-8.7]]
  11. === Breaking changes
  12. The following changes in {es} 8.7 might affect your applications
  13. and prevent them from operating normally.
  14. Before upgrading to 8.7, review these changes and take the described steps
  15. to mitigate the impact.
  16. There are no notable breaking changes in {es} 8.7.
  17. But there are some less critical breaking changes.
  18. [discrete]
  19. [[breaking_87_ingest_changes]]
  20. ==== Ingest changes
  21. [[making_jsonprocessor_stricter_so_it_does_not_silently_drop_data]]
  22. .Making `JsonProcessor` stricter so that it does not silently drop data
  23. [%collapsible]
  24. ====
  25. *Details* +
  26. The ingest node's `json` processor was previously lenient. It would accept invalid JSON data if it started with valid JSON data.
  27. Anything after the valid part would be silently discarded. From 8.7 onwards, the default behavior is to reject invalid JSON data with
  28. an exception so that data is not silently lost. The old behavior can be reproduced by passing `false` as the value of the new
  29. `strict_json_parsing` processor parameter.
  30. We consider this change to be a bugfix but list it here as a breaking change since it may affect the behavior of applications which
  31. were sending invalid JSON data to the `json` processor.
  32. *Impact* +
  33. Ensure your application only sends valid JSON data to the `json` processor, or modify the `json` processors in your pipelines to set
  34. the `strict_json_parsing` parameter to `false`.
  35. ====