Missing Support for term range queries

[lukapor]

Only number and date range queries are supported by version 8.

[flobernd]

I'm currently in the prgoress of implementing all missing endpoints and related features. This particular feature (term range queries) should be available afterwards as well.

[CasperWSchmidt]

@flobernd Any ETA on this? We're currently migrating from NEST because it's not working on .Net 8 and need the TermRangeQuery

[flobernd]

@CasperWSchmidt I hope to finish the required work on the code generator around end of Q1. If you can't use NEST and the v8.* client in parallel on .NET8, one workaround would be using the low level transport and manually crafting JSON requests. However, arsing the response could be challenging. As an alternative, you could probably fork NEST and add support for net8 (which shouldn't be a lot of work). This is what I've done a lot in the past for libraries which are no longer maintained.

[CasperWSchmidt]

@flobernd We're on a very tight schedule for upgrading to .Net 8, so we've chosen not to have support for term range queries for now and add it later. The end of Q1 sounds reasonable enough to just wait for it to come :)

[CasperWSchmidt]

@flobernd any news on this?

[flobernd]

Hi @CasperWSchmidt, as you've probably noticed, I was able to release the 8.13.x client in time. Afterwards I already started focusing on the bugs, but the list is long 🙂

It seems like this specific issue is related to the specification and not - like I originally thought - to the code generator. The TermsRangeQuery is not modelled there. I'm going to re-open issue until I come up with a fix.

[flobernd]

Related to elastic/elasticsearch-specification#2545