settings.asciidoc 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142
  1. [[breaking_70_settings_changes]]
  2. === Settings changes
  3. ==== Percolator
  4. * The deprecated `index.percolator.map_unmapped_fields_as_string` setting has been removed in favour of
  5. the `index.percolator.map_unmapped_fields_as_text` setting.
  6. ==== Index thread pool
  7. * Internally, single-document index/delete/update requests are executed as bulk
  8. requests with a single-document payload. This means that these requests are
  9. executed on the bulk thread pool. As such, the indexing thread pool is no
  10. longer needed and has been removed. As such, the settings
  11. `thread_pool.index.size` and `thread_pool.index.queue_size` have been removed.
  12. [[write-thread-pool-fallback]]
  13. ==== Write thread pool fallback
  14. * The bulk thread pool was replaced by the write thread pool in 6.3.0. However,
  15. for backwards compatibility reasons the name `bulk` was still usable as fallback
  16. settings `thread_pool.bulk.size` and `thread_pool.bulk.queue_size` for
  17. `thread_pool.write.size` and `thread_pool.write.queue_size`, respectively, and
  18. the system property `es.thread_pool.write.use_bulk_as_display_name` was
  19. available to keep the display output in APIs as `bulk` instead of `write`.
  20. These fallback settings and this system property have been removed.
  21. [[remove-http-enabled]]
  22. ==== Http enabled setting removed
  23. * The setting `http.enabled` previously allowed disabling binding to HTTP, only allowing
  24. use of the transport client. This setting has been removed, as the transport client
  25. will be removed in the future, thus requiring HTTP to always be enabled.
  26. [[remove-http-pipelining-setting]]
  27. ==== Http pipelining setting removed
  28. * The setting `http.pipelining` previously allowed disabling HTTP pipelining support.
  29. This setting has been removed, as disabling http pipelining support on the server
  30. provided little value. The setting `http.pipelining.max_events` can still be used to
  31. limit the number of pipelined requests in-flight.