mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-27 08:37:18 -04:00
cb402220d8
We deprecated `restoreShard` and `snapshotShard` in #42213 This change removes the deprecated methods and their usage and adds a note in the migration docs.
35 lines
1.3 KiB
Text
35 lines
1.3 KiB
Text
[float]
|
|
[[breaking_80_java_changes]]
|
|
=== Java API changes
|
|
|
|
//NOTE: The notable-breaking-changes tagged regions are re-used in the
|
|
//Installation and Upgrade Guide
|
|
|
|
//tag::notable-breaking-changes[]
|
|
|
|
// end::notable-breaking-changes[]
|
|
|
|
[float]
|
|
==== Changes to Fuzziness
|
|
|
|
To create `Fuzziness` instances, use the `fromString` and `fromEdits` method
|
|
instead of the `build` method that used to accept both Strings and numeric
|
|
values. Several fuzziness setters on query builders (e.g.
|
|
MatchQueryBuilder#fuzziness) now accept only a `Fuzziness`instance instead of
|
|
an Object. You should preferably use the available constants (e.g.
|
|
Fuzziness.ONE, Fuzziness.AUTO) or build your own instance using the above
|
|
mentioned factory methods.
|
|
|
|
Fuzziness used to be lenient when it comes to parsing arbitrary numeric values
|
|
while silently truncating them to one of the three allowed edit distances 0, 1
|
|
or 2. This leniency is now removed and the class will throw errors when trying
|
|
to construct an instance with another value (e.g. floats like 1.3 used to get
|
|
accepted but truncated to 1). You should use one of the allowed values.
|
|
|
|
|
|
[float]
|
|
==== Changes to Repository
|
|
|
|
Repository has no dependency on IndexShard anymore. The contract of restoreShard
|
|
and snapshotShard has been reduced to Store and MappingService in order to improve
|
|
testability.
|