Nest 7.6 -> GetManyAsync methos -> throw UnexpectedElasticsearchClientException
See original GitHub issueUsing 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.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (11 by maintainers)
Top Results From Across the Web
ElasticSearch Nest exception (Elasticsearch.Net. ...
In my separate solution everything works fine. The details of the exception is: Elasticsearch.Net.UnexpectedElasticsearchClientException: The ...
Read more >NEST Breaking Changes | Elasticsearch .NET Clients [7.17]
NET client exposes both synchronous and asynchronous API methods for both the ... and perform an action on an entity that does not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This fix will be going into
7.6.1
and6.8.5
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.