mappings.asciidoc 1.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. [float]
  2. [[breaking_80_mappings_changes]]
  3. === Mapping 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. [float]
  9. ==== Limiting the number of completion contexts
  10. The number of completion contexts within a single completion field
  11. has been limited to 10.
  12. [float]
  13. ==== Removal of types
  14. The typed REST endpoints of the Put Mapping, Get Mapping and Get Field mapping
  15. APIs have been removed in favour of their typeless REST endpoints, since indexes
  16. no longer contain types, these typed endpoints are obsolete.
  17. [float]
  18. ==== Defining multi-fields within multi-fields
  19. Previously, it was possible to define a multi-field within a multi-field.
  20. Defining chained multi-fields was deprecated in 7.3 and is now no longer
  21. supported. To migrate the mappings, all instances of `fields` that occur within
  22. a `fields` block should be removed, either by flattening the chained `fields`
  23. blocks into a single level, or by switching to `copy_to` if appropriate.
  24. [float]
  25. [[fieldnames-enabling]]
  26. ==== Disallow use of the `enabled` setting on the `_field_names` field
  27. The setting has been deprecated with 7.5 and is no longer supported on new indices.
  28. Mappings for older indices will continue to work but emit a deprecation warning.
  29. The `enabled` setting for `_field_names` should be removed from templates and mappings.
  30. Disabling _field_names is not necessary because it no longer carries a large index overhead.