BoolQuery Must, Must-Not and Should type is not consistent about elasticsearch-net HOT 4 CLOSED

Hi @deMD,

This behavior is defined in the specification and we refer to it as a "single or many" construct. For example: BoolQuery. While I agree that this is strange API design, there is not much I can do from my side (client). It might be the case, that in this particular place, an array with just a single element is accepted by the server, but that's not always the case.

Just a quick question:

I'm aware that there is no easy way to read the values stored in a descriptor and that even for regular request objects some values are inaccessible. I assume this is the reason you are trying to verify the query based on the JSON output?

from elasticsearch-net.

Ah too bad then. I'll make sure to have a nice workaround in our test suite for it then.

Yeah that is the reason we check the output. We are currently in the progress of upgrading from NEST to the new client, and want to make sure the requests to the server remain the same. The easiest way to do that is using VerifyTests and then comparing the json output just makes the most sense. A lot less hassle then coming up with a way to use reflection to do it.

from elasticsearch-net.

That's an interesting approach! Let me know if you encounter other discrepancies 🙂

from elasticsearch-net.

Will do! :)

from elasticsearch-net.