Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/ElasticLINQ/ElasticLINQ/releases below:

Releases · ElasticLINQ/ElasticLINQ · GitHub

This repository was archived by the owner on Jul 2, 2024. It is now read-only.

Releases · ElasticLINQ/ElasticLINQ

Available via NuGet at https://www.nuget.org/packages/ElasticLinq/1.4.3

• Object initializer syntax #106, e.g. Select(x => new User { Id = x.Id, Name = x.FullName })

• Allow nested properties to be selected individually in a Select #111
• LongCount no longer throws InvalidCastException #96

• Reduce memory usage by clearing batched results #95
• Reduce memory usage by hit collection after materialization #94
• Reduce memory usage by not creating dictionary for hits when not required ea4da60

• Updated Newtonsoft.JSON to 10.0.1
• Updated NSubstitute to 2.0.2
• Updated NuGet to 3.5.0
• Updated Elasticsearch.Net to 1.9.2

Available via NuGet at https://www.nuget.org/packages/ElasticLinq/1.4.2

• Binaries are now signed for strong naming purposes. The key is included so do not rely on this for trust.

• .Query operations containing an AND with two or more OR sub-clauses are correctly mapped into a nested bool query #

Available via NuGet at https://www.nuget.org/packages/ElasticLinq/1.4.1

• Internal changes to support Elasticsearch.Net connections via ElasticLINQ.ElasticsearchNet package
• Aggregate methods support where, e.g. users.Where(z => z.Zone > 1).Sum(z => z.Cost)

• Nested properties in the Couchbase mapper now create the correct field name
• NuGet package now specifies JSON.Net dependency so will bring it in if not already in use

• XML-comment documentation improvements

Available via NuGet at https://www.nuget.org/packages/ElasticLinq/1.4.0

• Async support for common LINQ & Enumerable methods e.g. ToListAsync, FirstAsync. #24
• Where filtering now generates a filtered query for improved performance #71
• Materialization of objects can be controlled via mapping interface #50
• Prefix operator can use a of string collection fields #75

If you implement IElasticMapping or override GetDocumentPrefix in your ElasticMapping subclass you will need to make changes. See the ElasticMapping concrete class for details on how document prefixes and materialization have changed.

If you inherited from ElasticMapping or CouchbaseMapping and did not implement your own GetDocumentPrefix no changes are necessary.

• XML-comment documentation improvements

Available via NuGet at https://www.nuget.org/packages/ElasticLinq/1.3.4

• Portable Class Library (PCL, Profile259) version included in NuGet package
• ElasticConnectionOptions.DefaultSearchSizeallows you to specify default size (number of results) for an Elasticsearch query without having to resort to Take (note the ES default is just 10) 673435e
• Support for Elasticsearch Highlighting #63

• Locally evaluated true or false subexpressions within Where or Query are recursively resolved before execution #66
• GroupBy can now group on a DateTime key 673435e

• Complete XML documentation for all public types 851e0dc

Available via NuGet at https://www.nuget.org/packages/ElasticLinq/1.3.1

• ElasticMethods.MinScore lets you specify a minimum score for your results

• Constants to the left of < > <= and >= operators are not inverted in the query #57
• Handle Unicode infinity symbols Double/Decimal/Single use on some platforms for +-Infinity when JSON decoding

• Updated to latest XUnit (2.0.0), BCL.Build (1.1.10), HTTP (2.2.29)

• Top-level Any() and Any(i => predicate) operators
• .Query now supports && and || by mapping them to bool queries
• .Query that evaluates to true or false locally is mapped to match_all or not(match_all) as appropriate
• [Required] attribute on properties now indicates to Couchbase-style mapping that a nullable field can be used for type selection by adding Exists criteria to the filter

• Returns correct document types for Couchbase-style mappings when Where was a null test
• More intelligent camel-casing of class property names to Elasticsearch document field names

• Updated to latest XUnit (2.0.0-rc1), JSON.NET (6.0.8), NSubstitute (1.8.1.0), BCL.Build (1.0.21)

The default ElasticMapping camel-cased JSON document properties from Pascal-case C# class properties by simply lower-casing the first letter.

A new algorithm now detects opening acronyms/all-caps. This means some properties such as "SSN", "ZIPCode" would have been "sSN" and "zIPCode". They are now "ssn" and "zipCode".

If you are using the Elasticsearch type system or the supplied CouchbaseMapper this change is not breaking for you.

This method was always called when no criteria existed in the tree. This meant it was sometimes not called when it should (e.g. Where(x => x.Something == null)

The new behavior is that his method is now always called and any non-null result is merged into the filter criteria.

https://www.nuget.org/packages/ElasticLinq/1.3.0

• Various facets by way of GroupBy/Count/Sum/Average/Min/Max etc.
• Counting the number of documents in a result via Count/LongCount
• HTTP GZip compression if available
• Deep property names and complex types
• String.StartsWith/Contains/EndsWith inside .Query predicates
• Nullability inside .Where maps to Exists/Missing

• Individual field selects now work on Elasticsearch 1.0+
• Dispose First/Single enumerator, ElasticContext etc.
• Honor JsonPropertyName on properties to specify field name

• Enums default to being string instead of integer
• Query info now available via ToQueryInfo().Body/Url rather than ToElasticSearchQuery()

• Project level support for PCL libraries (not in NuGet package yet)
• Updated to latest XUnit and JSON.NET
• Expanded unit tests and XML comment documentations

https://www.nuget.org/packages/ElasticLinq/1.2.0

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4