-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Queries are no longer derive from SearchQuery #8182
Comments
Hi @feherbbj, this is a change that was introduced with the new code generator. It was required to be able to generically support similar constructs in our specification. The container class The change is documented in the release notes of 8.13.0: |
Hi @flobernd , Thank you for the answer. I did not notice this breaking change, but even with your response I don't really understands the reason behind it. |
Hi @feherbbj, thanks for the feedback. Maybe this blog post gives you some more insights about the reasons: https://www.elastic.co/search-labs/blog/net-client-evolution It's basically just one person (me) maintaining the .NET client these days and we had to reduce scope to keep up with the workload. Now that version 8.13.x is released and finally most of the ES server APIs are supported, I can focus on bringing back some of the convenience features (but note, that bringing back NEST features is case by case decision and not everything will make it into the new client). |
Thanks for the info! Well that explains a lot. That's rough. Wishing you lots of perseverance then |
Elastic.Clients.Elasticsearch version: 8.13.x or 8.14
Elasticsearch version: 8.12.2
.NET runtime version: 8.0
Description of the problem including expected versus actual behavior:
Queries are no longer derive from SearchQuery ( I Mean TermsQuery, WildcardQuery...etc). Is there a reason for that? This way operators (&& or ||) cannot be applied. In earlier versions 8.12.0 or before they did derive from SearchQuery
Expected behavior
All query must derive from SearchQuery
The text was updated successfully, but these errors were encountered: