Upgrading NEST 0.12 to 1
Breaking0.12.0 → 1.9.2Breaking7Deprecated3New160Changed31Fixed169Other15
BreakingUpgrade verdict
7 breaking changes.
In plain terms
- new SearchRequest() now defaults to the configured default index, matching new SearchRequest<T>().
- Code that read the OK flag on responses must stop using it.
- The numeric range query type is gone because Elasticsearch no longer supports it.
- The scope option is gone from filters and facets, and nested filters now support joins.
Must act Top 5 of 10 that need code or config changes
What you must change
Breaking7
new SearchRequest() now defaults to the configured default index, matching new SearchRequest<T>().
SearchRequest()SearchRequest<T>()Removes all remaining OK properties from response types.
OKRemoves
NumericRangeQuery, which Elasticsearch removed in 0.90.8.NumericRangeQueryCompletely removes scope from filters and facets and implements join on nested filter.
Streamlines the Update APIs for consistency between Update and Bulk Update and better alignment with the Elasticsearch DSL.
Replaces the confusing ToggleSort() method with Order() on sort descriptors.
ToggleSort()Order()Range queries now only accept
GreaterThan(), GreaterThanOrEqual(), LowerThan() and LowerThanOrEqualTo().GreaterThan()GreaterThanOrEqual()LowerThan()LowerThanOrEqualTo()Deprecations to plan for
Deprecated3
Deprecates the Fuzziness ratio.
FuzzinessMarks the MultiField property descriptor obsolete.
MultiFieldMarks all references to BasicAuthorization as obsolete in favor of BasicAuthentication.
BasicAuthorizationBasicAuthentication