Nest 6.x GetAsync sets IsValid=false for 404 response

Elastic Stack Elasticsearch
1

We are updating from Nest and ElasticSearch 5.6 to 6.6 and have found that GetAsync sets IsValid=false when the document is not found. This is change from 5.6 where IsValid=true and Found=false. This is on .NET Core.

I can't find any information stating this change. And can't see how the exception could be used to infer it's valid but not found as it is simply an ElasticSearchClientException. Please advise if this is expected behaviour.

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.