32 lines
909 B
Plaintext
32 lines
909 B
Plaintext
|
[[breaking-changes-7.6]]
|
||
|
|
== Breaking changes in 7.6
|
||
|
|
++++
|
||
|
|
<titleabbrev>7.6</titleabbrev>
|
||
|
|
++++
|
||
|
|
|
||
|
|
This section discusses the changes that you need to be aware of when migrating
|
||
|
|
your application to Elasticsearch 7.6.
|
||
|
|
|
||
|
|
See also <<release-highlights>> and <<es-release-notes>>.
|
||
|
|
|
||
|
|
coming[7.6.0]
|
||
|
|
|
||
|
|
//NOTE: The notable-breaking-changes tagged regions are re-used in the
|
||
|
|
//Installation and Upgrade Guide
|
||
|
|
|
||
|
|
//tag::notable-breaking-changes[]
|
||
|
|
|
||
|
|
//end::notable-breaking-changes[]
|
||
|
|
|
||
|
|
[discrete]
|
||
|
|
[[breaking_76_search_changes]]
|
||
|
|
=== Search Changes
|
||
|
|
|
||
|
|
[discrete]
|
||
|
|
==== Deprecation of sparse vector fields
|
||
|
|
The `sparse_vector` field type has been deprecated and will be removed in 8.0.
|
||
|
|
We have not seen much interest in this experimental field type, and don't see
|
||
|
|
a clear use case as it's currently designed. If you have feedback or
|
||
|
|
suggestions around sparse vector functionality, please let us know through
|
||
|
|
GitHub or the 'discuss' forums.
|