1.1.0

New Features

Endpoints

• Added support for the multi percolate API
• Added support for alias exist API
• Added support for type exist API
• Added support for the explain API
• Added support for the snapshot status API
• Added support for the indices recovery API
• Added support for the cluster pending tasks API
• Added support for the cluster stats API
• Added support for the node shutdown API
• Added support for the Ping API
• Added missing PutAlias and DeleteAlias() endpoints #933, technically both of these were possible through the _aliases API already but we added them in for completion sake
• Added support for the template exist API
• Added support for the nodes hot_threads API
• Added support for the search shards API
• Added support for the get repository API
• Exposed DoRequest() on the NEST and Elasticsearch.NET clients so that you can hit any url while still taking advantage of the cluster failover and built in response handling #934
• NEST now also support ALL the _cat APIs

Aggregations

• percentile_ranks aggregation support #821
• geo_bounds aggregation support #822
• top_hits aggregation support #930
• reverse nested aggregation support #939

Updated APIs

• Added support for mapping field data formats for fields
• Added support for transform mapping
• Added a MappingVisitor class to walk over any elasticsearch mapping
• MoreLikeThisQuery() now supports ids and docs properties #894
• Added support for span_multi_term query #896

Bug Fixes

• Fixed an issue with parsing percentiles aggregation that prevented adjacent aggregations not to be parsed correctly #931
• HttpClientConnection (an HttpConnection alternative) now supports compressed responses and basic AUTH #947
• DateExpressionRange was missing the key property ty @taschmidt! #938
• Term filters did not serialize enums but only wrote there values reported on reopened #535
• Shard failures on responses did not include the reason property #930
• Fix occasions where Dictionary<valuetype, something> could not be mapped as object #926
• Elasticsearch.NET client is now generated from the 1.3.2 spec
• IndexOptions enum was missing Offsets option, ty @tbrooks007 ! #891
• In the IndicesStats API TypeNameMarker in the querystring were not resolved properly ty @Tasteful #908
• Fix #907 new SearchRequest() defaulted to all indices while new SearchRequest<T>() defaulted to the configured default index, the latter is now always the default behaviour for any OIS class.
• Count() now defaults to GET if no query is specified
• NEST now plays nicely with clusters that have the rest.action.multi.alow_explicit_index: false set for the various bulk endpoints (_bulk, _mget, _msearch et all). ty @Tasteful! #870
• Disable proxy detection now defaults to false, this means that NEST plays nicely with Fiddler out of the box. Either defaulting to true or false can cause an initial delay while .NET figures out whether a proxy is configured or not depending on your system, defaulting to false atleast has the added benefit of playing nice with fiddler see #866 for more background.
• A nested filter that only contained filters was marked as conditionless ty @Philo! #881
• NEST still used a special notation for multifield mapping, which meant that while generating the correct json it was hard to parse the mapping json back into C# objects. @Tasteful did an amazing job refactoring the mapping API in a backwards compatible manner so that you can branch off into multi_field mapping from any property mapping. see #885. Amazing work from @Tasteful!
• NEST 1.0 broke the ability to send a verbatim match query #876
• Some unit tests were missing invariant culure ty @Tasteful
• Various query string params were generated with an incorrect key see #858 for more background. ty @lakario for reporting this bug!
• Removed NetReflector as nuget dependency for Elasticsearch.Net.Connection.Thrift package
• Passing numeric collection to Terms filter and query resulted in a conditionless query #843
• Validated nuget package restore works correctly using all the new nuget goodness in Xamarin 5.3+
• @gmarz went over a great deal of the documentation and updated it to be correct following NEST 1.0. He also included a ton of examples using the object initializer syntax.
• @andersosthus added an advanced aggregation section to the documentation