Nest 7.6 -> GetManyAsync methos -> throw UnexpectedElasticsearchClientException

[meriturva]

Using latest version 7.6 we have few problems on tests that use GetManyAsync call.

For example:
var response = await this.Context.Client.GetManyAsync<TEntity>(ids, this.IndexName);

Just generate exception:

 Elasticsearch.Net.UnexpectedElasticsearchClientException : Index name is null for the given type and no default index is set. Map an index name using ConnectionSettings.DefaultMappingFor<TDocument>() or set a default index using ConnectionSettings.DefaultIndex().
    ---- System.ArgumentException : Index name is null for the given type and no default index is set. Map an index name using ConnectionSettings.DefaultMappingFor<TDocument>() or set a default index using ConnectionSettings.DefaultIndex().
  Stack Trace: 
    Transport`1.RequestAsync[TResponse](HttpMethod method, String path, CancellationToken cancellationToken, PostData data, IRequestParameters requestParameters) line 149
    GetManyExtensions.GetManyAsync[T](IElasticClient client, IEnumerable`1 ids, IndexName index, CancellationToken cancellationToken) line 68

Actually I could give you a more precise reproduction of the problem but not in a short time.
Tell me if necessary.

Ps: i reverted version to 7.5.1 and tests pass again.

[Mpdreamz]

Can reproduce this as well, will get a fix up shortly

[Mpdreamz]

@meriturva this should be fixed as per #4463

Are you able to give the following canary build a try?

NEST.7.6.0-ci20200226T122106

From this nuget feed:

https://ci.appveyor.com/nuget/elasticsearch-net

Thanks a ton for reporting this!

[meriturva]

Thanks @md right now I'm not able to change CI pipeline to include new feed source and really no time to test it locally (big project here).
If it is really necessary I will try tomorrow!

[Mpdreamz]

Not necessary :), was just curious if you could give it a quick spin.

We'll release new versions soon to nuget.org

[TheFireCookie]

I'm encountering the same bug. I'm glad it has already been corrected. When is a bugfix version planned to work? It prevents me to update to the latest, sweetest version for now.

[codebrain]

This fix will be going into 7.6.1 and 6.8.5