NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #1336 most downloaded on NuGet
NEST uses an internal serializer. This package enables serialization for your documents using your own custom Json.NET serializer
Latest stable
7.17.5
Last release 4 years ago
no release in 18 months
Ships fairly regularly
a new release about every 5 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
1 version withdrawn
withdrawn after publishing
127 years old
74 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
https://github.com/elastic/elasticsearch-net/compare/6.5.0...6.5.1
https://github.com/elastic/elasticsearch-net/compare/6.5.0...6.5.1
SniffingConnectionPool fails to make any request due to SniffResponse deserialization failureVoidResponse should not be sharedhttps://github.com/elastic/elasticsearch-net/compare/6.4.2...6.5.0
https://github.com/elastic/elasticsearch-net/compare/6.4.2...6.5.0
::Your coding agent can read these notes before it upgrades. Set up the MCP server →
Unfortunately, these were added in a binary breaking change, and slipped through into the 6.4.1 release. One of the core tenets of the client is to ma…
https://github.com/elastic/elasticsearch-net/compare/6.4.1...6.4.2
#3543 Include format in Field, Fields, Infer.Field FieldsDescriptor in a backwards binary compatible way
6.4.1 introduced an additional string format property to the constructors of Field, Fields, Infer.Field and FieldsDescriptor. Unfortunately, these were added in a binary breaking change, and slipped through into the 6.4.1 release. One of the core tenets of the client is to maintain binary compatibility across a major version of the client.
6.4.2 introduces format in a binary backward compatible way, fixing the issue with 6.4.1. The 6.4.1 package has been unlisted in nuget, and we recommend upgrading to the latest version of the client as soon as possible.
https://github.com/elastic/elasticsearch-net/compare/6.4.0...6.4.1
https://github.com/elastic/elasticsearch-net/compare/6.4.0...6.4.1
The rest of the commits are all related to housekeeping, moving FAKE build tasks to dedicated dotnet tools
https://github.com/elastic/elasticsearch-net/compare/6.3.1...6.4.0
https://github.com/elastic/elasticsearch-net/compare/6.3.1...6.4.0
https://github.com/elastic/elasticsearch-net/compare/6.3.0...6.3.1
https://github.com/elastic/elasticsearch-net/compare/6.3.0...6.3.1
JsonNetSerializerhttps://github.com/elastic/elasticsearch-net/compare/6.2.0...6.3.0
https://github.com/elastic/elasticsearch-net/compare/6.2.0...6.3.0
This release brings feature parity with Elasticsearch 6.3.0. Support for the Roll Up API is not part of this release and will be forthcoming in 6.4.0 releases of the .NET clients.
This release also changes our supported TFM from net45 and netstandard1.3 to net461 and netstandard2.0.
netstandard2.0 will produce a cleaner dependency graph and we bumped to net461 as the new baseline for Full Framework so that we can reuse almost all the code between the two TFM's. The only difference between the two TFM's is that net461 uses an HttpConnection built on top of HttpWebRequest and netstandard2.0 builds on top of HttpClient. HttpWebRequest exists on .NET core 2.0 but should not be used.
For 6.4.0 we are investigating supporting a netcoreapp2.1 TFM which can take advantage of the new managed handler for HttpClient and will be looking to move our HttpClient based connection over to HttpClientFactory. Our implementation does much of the same HttpClientFactory does but why maintain if we can depend on something else. With these plans we felt the need to bump net45 to net461 to restrain our multi-platform support. We feel that most greenfield projects should be on net461 and later and the upgrade from net45 to net461 on servers is fully backwards compatible. Please let us know if you are in a situation where you are not able to upgrade.
Comparison of https://github.com/elastic/elasticsearch-net/compare/6.2.0...6.3.0
allow_partial_search_results search request parameter## Features & Enhancements - #3279 6.x Performance Improvements - #3277 Associate an external id with a task, so that it can be cancelled later. - #32
jarowinkler in favor of jaro_winklerlevenstein in favor of levensHteinwait_for_no_initializing_shards to cluster health APIhttps://github.com/elastic/elasticsearch-net/compare/6.0.2...6.1.0
https://github.com/elastic/elasticsearch-net/compare/6.0.2...6.1.0
ip_range range datatypeauto_generate_synonyms_phrase_query parametermax_token_length to Whitespace tokenizerwait_for_active_shards parameter to index open commandignore_malformed to geo_shape fieldmax_size to Rollover API conditionsReIndexOnServerPhoneticEncodernested sort and deprecate nested_path and nested_filtertext fieldsFields to be optional on MultiMatchQueryignore_unmapped to inner_hitsskip_duplicates to Completion Suggesternested sort and deprecate nested_path and nested_filterIndicesBoost as array instead of object, allowing ordered precedence to boosting.IgnoreUnmapped on IGeoShapeIGeoShape types on documentsIndexed property to GenericProperty to support correct index optionsserver_side_encryption to s3 repository settingsJsonConverters added to JsonSerializerSettingsVisit() methods to IPropertyVisitor and IMappingVisitior for range data typesDecision enumhttps://github.com/elastic/elasticsearch-net/compare/6.0.1...6.0.2
https://github.com/elastic/elasticsearch-net/compare/6.0.1...6.0.2
This release bumps the JSON.NET dependency of NEST.JsonNetSerializer to 11.x (#3115)
Additional bug fixes:
It is recommended to update to 6.0.1 due to #3084.
It is recommended to update to 6.0.1 due to #3084.
Dictionary<string,object>Also check out 5.x -> 6.x breaking changes
A huge thank you to the community who kicked the tires on the 6.0 prereleases that we've been putting out and providing invaluable feedback 🖖
Check out the blog post on the NEST 6.0 release that highlights some of the main features within this major release.
Also check out 5.x -> 6.x breaking changes
BulkAll pluggableServerErrorexplain on Analyze APIphrase_limit for FVH highlighting"missing" fieldextended_bounds type on Date Histogram aggregations. Thanks @FabienLavocat 👍shard_min_doc_count parameter on Significant Terms Aggregation.params property to phrase_suggest_collate.The second release of the Elastic .NET packages, to address issues found by customers in the 6.0.0-beta1 release.
The second release of the Elastic .NET packages, to address issues found by customers in the 6.0.0-beta1 release.
These packages are designed to be used in conjunction with Elasticsearch 6.x
{dynamic_type} as part of the mappingtype on has_parent query should be parent_typeThe breaking changes for Elasticsearch 5.x to 6.x are documented here and tracked here.
These beta packages have been released in order to solicit feedback from users. Like any beta software it should not be used in a production environment, if you do so it is very much at your own risk and we will be unable to support you.
These packages are designed to be used in conjunction with Elasticsearch 6.x
We are, however, very keen to field any issues that you may have. If you come across a problem please open an issue. Please ensure your issue mentions the 6.0.0-beta1 label.
The Newtonsoft.Json nuget dependency has been removed and the assembly has now been IL merged into the NEST assembly.
The reasons for this are two-fold:
The Json.NET library has been completely internalized. All methods, properties, classes (etc) have been rewritten into the NEST assembly with internal scope and namespaces moved over to NEST.Json. It should not be possible to access any of the serialization functionality and it should coexist with Newtonsoft.Json references in your project.
The new NEST.JsonNetSerializer package enables you to write a custom serialization path for the types you index into Elasticsearch using Json.NET.
This creates a new extension point within NEST for the serialization of your types.
It is now only possible to have a single type per index, this change is more heavily documented here.
If you have multiple types in an index you'll need to move to a single type per index solution. If you can not do that straight away you can opt in to multiple types, for the time being, by using mapping.single_type index settings.
new IndexSettings(new Dictionary<string, object> {
{ "mapping.single_type", "false" }
})
{
NumberOfShards = 2,
NumberOfReplicas = 0,
};
The breaking changes for Elasticsearch 5.x to 6.x are documented here and tracked here.
One column per quarter.