You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem including expected versus actual behavior:
After upgrading to the new client, Ping method fails either with previous or minimal configuration.
While debugging I tracked it down to this line in HttpTransportClient method public override TResponse Request<TResponse>(RequestData requestData):
This has recently been fixed in elastic/elastic-transport-net#78, and we will need to update to the latest patch to pick up this fix. @VMelnalksnis In the mean time, as this only affected the sync path, PingAsync should work for you and would be recommended as best practice.
Elastic.Clients.Elasticsearch version: 8.1.1
Elasticsearch version: 8.6.1
.NET runtime version: 6.0
Operating system version: Windows 10 22H2
Description of the problem including expected versus actual behavior:
After upgrading to the new client,
Ping
method fails either with previous or minimal configuration.While debugging I tracked it down to this line in
HttpTransportClient
methodpublic override TResponse Request<TResponse>(RequestData requestData)
:The exception is thrown because the response content does not have any headers.
Steps to reproduce:
ElasticsearchClient
with the settings belowElasticsearchClient.Ping()
UnexpectedTransportException
with innerNullReferenceException
Expected behavior
Ping succeeds.
Provide
ConnectionSettings
(if relevant):The text was updated successfully, but these errors were encountered: