Florian Bernd

Hi @Bhavyagc02, as explained in the changelog, this is still possible, but the structure changed a bit: ```csharp await client.SearchAsync(x => x .Aggregations(aggs => aggs .Add("filtersagg", agg => agg .Filters(f...

Hi @Bhavyagc02 , did that answer your question?

Hi @Lukyb14, I can not reproduce this issue. I assume the way you are building the query is incorrect. The following code: ```csharp var termSuggester = FieldSuggester.Term(new TermSuggester { Analyzer...

@Lukyb14 We double checked and it seems like the text property was indeed incorrectly added to these two suggester variants. I'll make sure to remove them from our specification 🙂...

This sounds a little bit like the "multi" version of what's described in #7792

> Is there a roadmap / timeframe for when this will be implemented? I know there's a workaround to simply not use named filters but wasn't sure of the position...

Hi @Leandore, the changelog/documentation is currently not automatically generated by the release workflow. This is on my roadmap. For now, you can always check the release notes of the [GitHub...

@apr-un I will update the issue if there is any progress.

Hi @niemyjski, thank you for the detailed feedback. Quite a few of these design decisions were made before I took over the maintainer role for the .NET clients. It probably...

Hi @krasheninnik, this is a similar case as described in #8184 Currently this is the expected behavior as stated [here](https://github.com/elastic/elasticsearch-net/issues/8184#issuecomment-2102407079). However, it seems like this is not what users intuitively...