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:
I'm upgrading from NEST 7.latest to the new Elastic.Clients.Elasticsearch version.
And I'm missing some features that are not yet supported
Steps to reproduce:
Create code to call the Get index settings API
var result = await Client.Indices.GetSettingsAsync(s => s
.Indices(indexName)
.Name("index.analysis.filter." + filterName + ".*")
);
Trying to parse the response to get a specific setting:
var indexState = result?.Indices?[indexName];
Expected behavior
In the NEST 7 version, this was easily done
In the Elastic.Client.Elasticsearch 8 it seams that all .net properties are protected and not accesable
Please make sure that this code is backwards compatible with minor effort
Provide ConnectionSettings (if relevant):
Provide DebugInformation (if relevant):
The text was updated successfully, but these errors were encountered:
Elastic.Clients.Elasticsearch version:
8.13.5
Elasticsearch version:
N/A
.NET runtime version:
.Net 8.0
Operating system version:
N/A
Description of the problem including expected versus actual behavior:
I'm upgrading from NEST 7.latest to the new Elastic.Clients.Elasticsearch version.
And I'm missing some features that are not yet supported
Steps to reproduce:
var result = await Client.Indices.GetSettingsAsync(s => s
.Indices(indexName)
.Name("index.analysis.filter." + filterName + ".*")
);
var indexState = result?.Indices?[indexName];
Expected behavior
In the NEST 7 version, this was easily done
In the Elastic.Client.Elasticsearch 8 it seams that all .net properties are protected and not accesable
Please make sure that this code is backwards compatible with minor effort
Provide
ConnectionSettings
(if relevant):Provide
DebugInformation
(if relevant):The text was updated successfully, but these errors were encountered: