Skip to content

Releases: elastic/elasticsearch-net

9.1.10

07 Oct 19:56
bb47ea7
Compare
Choose a tag to compare

What's Changed

  • Allow Esql.QueryAsObjects() to work with nested types by @flobernd in #8729

Full Changelog: 9.1.9...9.1.10

8.19.9

07 Oct 19:56
33f13f4
Compare
Choose a tag to compare

What's Changed

  • Allow Esql.QueryAsObjects() to work with nested types by @flobernd in #8729

Full Changelog: 8.19.8...8.19.9

9.1.9

29 Sep 14:02
03f92c0
Compare
Choose a tag to compare

What's Changed

  • Switch to custom SafeSkip() method that works with partial JSON blocks by @flobernd in #8720
    • Improves compatibility in certain streaming scenarios

Full Changelog: 9.1.8...9.1.9

8.19.8

29 Sep 14:02
c5bea54
Compare
Choose a tag to compare

What's Changed

  • Switch to custom SafeSkip() method that works with partial JSON blocks by @flobernd in #8720
    • Improves compatibility in certain streaming scenarios

Full Changelog: 8.19.7...8.19.8

9.1.8

25 Sep 12:40
81cebf5
Compare
Choose a tag to compare

What's Changed

Breaking Changes

The type of the Sources property has been changed from ICollection<IDictionary<string, CompositeAggregationSource>> to ICollection<KeyValuePair<string, CompositeAggregationSource>>. This corresponds to the Elasticsearch standard for modeling ordered dictionaries in the REST API.

CompositeAggregationSource is now also a container (similar to Aggregation, Query, etc.). This change improves usability due to specialized code generation. For example, implicit conversion operators from all existing variants (CompositeTermsAggregation, CompositeHistogramAggregation, etc.) to CompositeAggregationSource are now generated.

As a consequence, the object initializer syntax changes as follows:

// 9.1.7 and below

var request = new SearchRequest
{
    Aggregations = new Dictionary<string, Aggregation>
    {
        { "my_composite", new CompositeAggregation
        {
            Sources =
            [
                new Dictionary<string, CompositeAggregationSource>
                {
                    { "my_terms", new CompositeAggregationSource
                    {
                        Terms = new CompositeTermsAggregation
                        {
                            // ...
                        }
                    }}
                },
                new Dictionary<string, CompositeAggregationSource>
                {
                    { "my_histo", new CompositeAggregationSource
                    {
                        Histogram = new CompositeHistogramAggregation(0.5)
                        {
                            // ...
                        }
                    }}
                }
            ]
        }}
    }
};

// 9.1.8 and above

var request = new SearchRequest
{
    Aggregations = new Dictionary<string, Aggregation>
    {
        { "my_composite", new CompositeAggregation
        {
            Sources =
            [
                new KeyValuePair<string, CompositeAggregationSource>(
                    "my_terms",
                    // Implicit conversion from `CompositeTermsAggregation` to `CompositeAggregationSource`.
                    new CompositeTermsAggregation
                    {
                        // ...
                    }
                ),
                new KeyValuePair<string, CompositeAggregationSource>(
                    "my_histo",
                    // Implicit conversion from `CompositeHistogramAggregation` to `CompositeAggregationSource`.
                    new CompositeHistogramAggregation(0.5) <2>
                    {
                        // ...
                    }
                )
            ]
        }}
    }
};

In addition, this change allows optimized Fluent syntax to be generated, which ultimately avoids a previously existing ambiguity:

// 9.1.7 and below

var descriptor = new SearchRequestDescriptor()
    .Aggregations(aggs => aggs
        .Add("my_composize", agg => agg
            .Composite(composite => composite
                // This is the `params` overload that initializes the `Sources` collection with multiple entries.
                .Sources(
                    // Add dictionary item 1 that contains a single `Terms` aggregation entry.
                    x => x.Add("my_terms", x => x.Terms(/* ... */)),
                    // Add dictionary item 2 that contains a single `Histogram` aggregation entry.
                    x => x.Add("my_histo", x => x.Histogram(/* ... */)) <3>
                )
            )
        )
    );

// 9.1.8 and above

var descriptor = new SearchRequestDescriptor()
    .Aggregations(aggs => aggs
        .Add("my_composize", agg => agg
            .Composite(composite => composite
                .Sources(sources => sources
                    .Add("my_terms", x => x.Terms(/* ... */))
                    .Add("my_histo", x => x.Histogram(/* ... */))
                )
            )
        )
    );

The old syntax was tricky because the 9.1.8 example also compiled successfully, but the .Add referred to the first dictionary both times. This ultimately resulted in a list with only one dictionary, which had multiple entries, and thus an invalid request.


Full Changelog: 9.1.7...9.1.8

8.19.7

25 Sep 12:45
59f8977
Compare
Choose a tag to compare

What's Changed

Breaking Changes

See https://github.com/elastic/elasticsearch-net/releases/tag/9.1.8.


Full Changelog: 8.19.6...8.19.7

9.1.7

11 Sep 15:00
40ce798
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 9.1.6...9.1.7

8.19.6

11 Sep 15:01
7da1703
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 8.19.5...8.19.6

9.1.6

29 Aug 12:52
5197a92
Compare
Choose a tag to compare

What's Changed

Full Changelog: 9.1.5...9.1.6

8.19.5

29 Aug 12:51
3cca372
Compare
Choose a tag to compare

What's Changed

Full Changelog: 8.19.4...8.19.5